From: Jonathan Nieder <jrnieder@gmail.com>
To: stable@vger.kernel.org
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
Mi Jinlong <mijinlong@cn.fujitsu.com>,
NFSv3 list <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@redhat.com>,
Jeff Layton <jlayton@redhat.com>,
Chuck Lever <chuck.lever@oracle.com>,
Tom Downes <tpdownes@gravity.phys.uwm.edu>
Subject: [2.6.32.y, 2.6.34.y] Re: kernel panic when mount NFSv4
Date: Thu, 13 Dec 2012 21:39:58 -0800 [thread overview]
Message-ID: <20121214053958.GA4002@elie.Belkin> (raw)
In-Reply-To: <1292879966.7744.4.camel@heimdal.trondhjem.org>
Hi Willy et al,
Please consider
beb0f0a9fba1 kernel panic when mount NFSv4, 2010-12-20
for application to kernel.org's 2.6.32.y and 2.6.34.y trees. The
patch was applied upstream during the 2.6.38 merge window, so newer
kernels don't need it.
(Context: <http://bugs.debian.org/695872>.) Tom Downes (cc-ed)
experienced the bug on a Debian kernel close to 2.6.32.58 and
confirmed that the patch doesn't seem to hurt.
The patch is part of Fedora 13's 2.6.34-based and Fedora 14's
2.6.35-based kernels[1]. It was also included in the RHEL kernel at
some point between 2.6.32-71.29.1.el6 and 2.6.32-131.0.15.el6[2].
Thoughts of all kinds welcome, as always.
Regards,
Jonathan
[1] https://bugzilla.redhat.com/673207
[2] https://oss.oracle.com/git/?p=redpatch.git;a=commit;h=8028cccdc4b1
next prev parent reply other threads:[~2012-12-14 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 8:58 kernel panic when mount NFSv4 Mi Jinlong
2010-12-20 10:01 ` Mi Jinlong
2010-12-20 21:19 ` Trond Myklebust
2010-12-21 5:38 ` Mi Jinlong
2012-12-14 5:39 ` Jonathan Nieder [this message]
2012-12-14 7:17 ` [2.6.32.y, 2.6.34.y] " Willy Tarreau
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=20121214053958.GA4002@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mijinlong@cn.fujitsu.com \
--cc=stable@vger.kernel.org \
--cc=tpdownes@gravity.phys.uwm.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 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).