diff options
| author | Anton Blanchard <anton@samba.org> | 2012-03-16 10:28:19 +0000 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-03-16 17:01:41 -0700 |
| commit | c0173863528a8c9212c53e080d63a1aaae5ef4f4 (patch) | |
| tree | 6e63b069354fdf8c9a21f1560da8720d32149a80 /arch | |
| parent | 2c724fb92732c0b2a5629eb8af74e82eb62ac947 (diff) | |
| download | blackbird-obmc-linux-c0173863528a8c9212c53e080d63a1aaae5ef4f4.tar.gz blackbird-obmc-linux-c0173863528a8c9212c53e080d63a1aaae5ef4f4.zip | |
afs: Remote abort can cause BUG in rxrpc code
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>
Cc: <stable@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions
