From: Ben Greear <greearb@candelatech.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Jim Rees <rees@umich.edu>, Chris Rankin <rankincj@yahoo.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [OOPS] NFS dereferenced NULL pointer with 3.2.6 kernel.
Date: Mon, 20 Feb 2012 11:16:04 -0800 [thread overview]
Message-ID: <4F429BF4.9050409@candelatech.com> (raw)
In-Reply-To: <1329764945.5151.13.camel@lade.trondhjem.org>
On 02/20/2012 11:09 AM, Myklebust, Trond wrote:
> On Mon, 2012-02-20 at 10:43 -0800, Ben Greear wrote:
>> On 02/20/2012 10:35 AM, Myklebust, Trond wrote:
>>> On Mon, 2012-02-20 at 13:27 -0500, Jim Rees wrote:
>>>> Myklebust, Trond wrote:
>>>>
>>>> It's a known bug. There is a fix at
>>>>
>>>> http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git;a=commit;h=331818f1c468a24e581aedcbe52af799366a9dfe
>>>>
>>>> Shouldn't this be in stable by now? You sent it Feb 3, and there have been
>>>> two stable releases since then.
>>>
>>> I've been waiting for Andy to get back from vacation. We've already sent
>>> one buggy patch to stable...
>>>
>>
>> It's still not in 3.3-rc either, at least put it there so others
>> can test it?
>
> 3.3-rc is _NOT_ a place to put patches for testing... You test the
> patches _BEFORE_ you send them upstream.
Ok, but seems like it would be pretty lame to release 3.3 with this known
crash bug.
And, though I haven't done any thorough NFS testing, I could hit the
bug every time before I applied the patch..and since I applied it,
I have not had any problems.
So, it has been tested at least a bit.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-02-20 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 0:33 [OOPS] NFS dereferenced NULL pointer with 3.2.6 kernel Chris Rankin
2012-02-20 2:01 ` Jim Rees
2012-02-20 18:00 ` Myklebust, Trond
2012-02-20 18:00 ` Myklebust, Trond
2012-02-20 18:27 ` Jim Rees
2012-02-20 18:35 ` Myklebust, Trond
2012-02-20 18:43 ` Ben Greear
2012-02-20 19:09 ` Myklebust, Trond
2012-02-20 19:16 ` Ben Greear [this message]
2012-02-20 19:33 ` Andy Adamson
2012-02-20 20:53 ` Jim Rees
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=4F429BF4.9050409@candelatech.com \
--to=greearb@candelatech.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rankincj@yahoo.com \
--cc=rees@umich.edu \
/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.