From: Jim Rees <rees@umich.edu>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [OOPS] NFS dereferenced NULL pointer with 3.2.6 kernel.
Date: Sun, 19 Feb 2012 21:01:48 -0500 [thread overview]
Message-ID: <20120220020148.GB20376@umich.edu> (raw)
In-Reply-To: <4F4194C4.40104@yahoo.com>
Chris Rankin wrote:
My 3.2.6 (x86, 32 bit) kernel oopsed last night while pulling a file
across an NFS mount:
I think this is fixed by commit 331818f1c4, "Fix an Oops in the NFSv4 getacl
code." Shouldn't this be in stable by now? It doesn't seem to be.
next prev parent reply other threads:[~2012-02-20 2:01 UTC|newest]
Thread overview: 10+ 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 [this message]
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
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=20120220020148.GB20376@umich.edu \
--to=rees@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rankincj@yahoo.com \
/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).