From: Benny Halevy <bhalevy@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: pnfs-all-latest client crash
Date: Thu, 30 Sep 2010 17:34:18 +0200 [thread overview]
Message-ID: <4CA4ADFA.2090807@panasas.com> (raw)
In-Reply-To: <20100930152944.GA6598@fieldses.org>
On 2010-09-30 17:29, J. Bruce Fields wrote:
> On Thu, Sep 30, 2010 at 05:25:33PM +0200, Benny Halevy wrote:
>> On 2010-09-21 21:01, J. Bruce Fields wrote:
>>> On Tue, Sep 21, 2010 at 08:43:15PM +0200, Benny Halevy wrote:
>>>> On 2010-09-21 18:42, J. Bruce Fields wrote:
>>>>> I get the following on pnfs-all-latest, while doing a non-pnfs 4.1 mount.
>>>>
>>>> Bruce, can you please provide you .config file?
>>>> >From the registers value it's possible the calldata is used
>>>> after free...
>>>
>>> Yep. I ran a 'make oldconfig' on the appended and built from that.
>>>
>>> We've seen poisoning in trond's latest for-next as well. Which I don't
>>> think you're including. But I'll add linux-nfs to the cc for that.
>>>
>>> --b.
>>>
>>> #
>>> # Automatically generated make config: don't edit
>>> # Linux kernel version: 2.6.36-rc4
>>> # Wed Sep 15 14:57:18 2010
>>> #
> ...
>>> # CONFIG_INPUT_TABL
>>
>> Looks like the message got truncated :-(
>
> Huh. Sorry about that!
And I presume you config all pNFS options as 'N', right?
Benny
>
> --b.
>
next prev parent reply other threads:[~2010-09-30 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 16:42 pnfs-all-latest client crash J. Bruce Fields
2010-09-21 18:43 ` Benny Halevy
2010-09-21 19:01 ` J. Bruce Fields
2010-09-28 15:51 ` J. Bruce Fields
2010-09-29 15:34 ` Benny Halevy
2010-09-30 13:15 ` J. Bruce Fields
2010-09-30 13:24 ` Benny Halevy
2010-09-30 13:28 ` J. Bruce Fields
2010-09-30 15:25 ` Benny Halevy
2010-09-30 15:29 ` J. Bruce Fields
2010-09-30 15:34 ` Benny Halevy [this message]
2010-09-30 15:43 ` J. Bruce Fields
2010-09-30 19:52 ` Benny Halevy
2010-10-01 17:07 ` J. Bruce Fields
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=4CA4ADFA.2090807@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@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