From: Mark Moseley <moseleymark@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux filesystem caching discussion list
<linux-cachefs@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-cachefs] 3.0.3 64-bit Crash running fscache/cachefilesd
Date: Thu, 29 Sep 2011 12:02:47 -0700 [thread overview]
Message-ID: <CAOH1cHmFuXn3uZbyZy94-cBGCPDxLsJuskkYRteeBs75iLhssw@mail.gmail.com> (raw)
In-Reply-To: <12748.1317313818@redhat.com>
On Thu, Sep 29, 2011 at 9:30 AM, David Howells <dhowells@redhat.com> wrote:
> Mark Moseley <moseleymark@gmail.com> wrote:
>
>> >> [12999.564897] FS-Cache: Cookie 'NFS.fh' still has outstanding reads
>> >
>> > Hopefully the patch set I sent to you will deal with this.
>> >
>> > David
>>
>> Not sure what you mean. Was there another patch besides the one to get
>> more info in the traceback?
>
> I emailed a set of 13 patches to you a short time before that. Hopefully
> they'll fix the outstanding-reads problem the bad-page-state problem.
Sorry, I just had this thread sitting open in gmail and I was looking
for the patch within it. I see all those emails you sent. I'll try to
get those patched in today. Thanks!
next prev parent reply other threads:[~2011-09-29 19:02 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 [this message]
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
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=CAOH1cHmFuXn3uZbyZy94-cBGCPDxLsJuskkYRteeBs75iLhssw@mail.gmail.com \
--to=moseleymark@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.