From: David Howells <dhowells@redhat.com>
To: Linux filesystem caching discussion list <linux-cachefs@redhat.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [Linux-cachefs] 3.0.3 64-bit Crash running fscache/cachefilesd
Date: Fri, 30 Sep 2011 21:10:15 +0100 [thread overview]
Message-ID: <29780.1317413415@redhat.com> (raw)
In-Reply-To: <CAOH1cHkVjTSBvqvaoWnxTB1V-dOtj1cCT_kMZpJdsyNNeUoBag@mail.gmail.com>
Mark Moseley <moseleymark@gmail.com> wrote:
> [ 6052.503856] [kworke] <== __fscache_write_page() = -ENOBUFS [invalidating]
Nothing to worry about. I have some kleave() calls to turn into _leave().
> [ 7720.060050] [<ffffffff81197b24>] fscache_put_operation+0x304/0x330
> [ 7720.060050] [<ffffffff81197b8b>] fscache_op_work_func+0x3b/0xd0
> [ 7720.060050] [<ffffffff810660c4>] process_one_work+0x164/0x440
> [ 7720.060050] [<ffffffff81197b50>] ? fscache_put_operation+0x330/0x330
> [ 7720.060050] [<ffffffff8106674b>] worker_thread+0x19b/0x430
> [ 7720.060050] [<ffffffff810665b0>] ? manage_workers+0x210/0x210
> [ 7720.060050] [<ffffffff8106d11e>] kthread+0x9e/0xb0
> [ 7720.060050] [<ffffffff8162d4f4>] kernel_thread_helper+0x4/0x10
> [ 7720.060050] [<ffffffff8162ab8a>] ? retint_restore_args+0xe/0xe
> [ 7720.060050] [<ffffffff8106d080>] ? kthread_worker_fn+0x190/0x190
> [ 7720.060050] [<ffffffff8162d4f0>] ? gs_change+0xb/0xb
Hmmm... That's a new one. Looks like I've missed another op put.
Thanks for testing!
David
next prev parent reply other threads:[~2011-09-30 20:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 16:44 3.0.3 64-bit Crash running fscache/cachefilesd Mark Moseley
2011-08-26 12:52 ` [Linux-cachefs] " Дмитрий Ильин
2011-09-01 13:04 ` David Howells
2011-09-22 17:03 ` Mark Moseley
2011-09-22 21:41 ` Mark Moseley
2011-09-26 11:32 ` David Howells
2011-09-26 21:02 ` Mark Moseley
2011-09-27 0:59 ` Mark Moseley
2011-09-27 23:46 ` Mark Moseley
2011-09-29 14:57 ` David Howells
2011-09-29 15:51 ` Mark Moseley
2011-09-29 16:30 ` David Howells
2011-09-29 19:02 ` Mark Moseley
2011-09-29 22:11 ` Mark Moseley
2011-09-29 22:44 ` Mark Moseley
2011-09-29 22:44 ` David Howells
2011-09-29 22:51 ` Mark Moseley
2011-09-30 12:28 ` David Howells
2011-09-30 18:57 ` Mark Moseley
2011-09-30 20:10 ` David Howells [this message]
2011-10-05 13:37 ` David Howells
2011-10-05 13:49 ` David Howells
2011-10-07 10:42 ` David Howells
2011-10-08 16:32 ` Mark Moseley
2011-10-11 13:07 ` David Howells
2011-10-11 16:27 ` Mark Moseley
2011-10-12 9:26 ` David Howells
2011-10-12 10:05 ` David Howells
2011-10-12 18:10 ` Mark Moseley
2011-10-12 23:38 ` Mark Moseley
2011-10-13 15:21 ` David Howells
2011-10-13 20:48 ` Mark Moseley
2011-10-14 9:22 ` David Howells
2011-10-14 23:25 ` Mark Moseley
2011-10-17 10:39 ` David Howells
2011-10-19 12:25 ` David Howells
2011-10-19 23:15 ` Mark Moseley
2011-10-20 8:46 ` David Howells
2011-10-20 19:37 ` Mark Moseley
2011-10-20 9:03 ` David Howells
2011-10-20 19:29 ` Mark Moseley
2011-10-20 23:05 ` David Howells
2011-10-21 0:21 ` Mark Moseley
2011-10-21 8:16 ` David Howells
2011-10-21 18:09 ` Mark Moseley
2011-12-13 1:56 ` Mark Moseley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29780.1317413415@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).