aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2012-03-16 10:28:19 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-03-23 11:20:51 -0700
commit086b5909dfe7c79b68ed76d798a30dfc7c329852 (patch)
treebd98c540288d48795bcc8f18d61d88686f0a824c /tools
parent4376d0751532595d76d8dbe9a7ddb6d92f08ff82 (diff)
downloadkernel_samsung_smdk4412-086b5909dfe7c79b68ed76d798a30dfc7c329852.zip
kernel_samsung_smdk4412-086b5909dfe7c79b68ed76d798a30dfc7c329852.tar.gz
kernel_samsung_smdk4412-086b5909dfe7c79b68ed76d798a30dfc7c329852.tar.bz2
afs: Remote abort can cause BUG in rxrpc code
commit c0173863528a8c9212c53e080d63a1aaae5ef4f4 upstream. When writing files to afs I sometimes hit a BUG: kernel BUG at fs/afs/rxrpc.c:179! With a backtrace of: afs_free_call afs_make_call afs_fs_store_data afs_vnode_store_data afs_write_back_from_locked_page afs_writepages_region afs_writepages The cause is: ASSERT(skb_queue_empty(&call->rx_queue)); Looking at a tcpdump of the session the abort happens because we are exceeding our disk quota: rx abort fs reply store-data error diskquota exceeded (32) So the abort error is valid. We hit the BUG because we haven't freed all the resources for the call. By freeing any skbs in call->rx_queue before calling afs_free_call we avoid hitting leaking memory and avoid hitting the BUG. Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: David Howells <dhowells@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions