From: Greg KH <greg@kroah.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Jesper Krogh <jesper-Q2TZfHgGEy4@public.gmane.org>,
autofs-CPWUtch7KCBzeIdxy0IIJw@public.gmane.org,
linux-nfs@vger.kernel.org, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Linux 2.6.27.13
Date: Wed, 28 Jan 2009 16:37:12 -0800 [thread overview]
Message-ID: <20090129003712.GC23732@kroah.com> (raw)
In-Reply-To: <1233171227.9785.28.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Wed, Jan 28, 2009 at 02:33:47PM -0500, Trond Myklebust wrote:
> On Wed, 2009-01-28 at 13:58 +0100, Jesper Krogh wrote:
> > Greg KH wrote:
> > > We (the -stable team) are announcing the release of the 2.6.27.13
> > > kernel.
> > >
> > > It contains a wide range of bugfixes, and all users of the 2.6.27 kernel
> > > series are strongly encouraged to upgrade.
> > >
> > > I'll also be replying to this message with a copy of the patch between
> > > 2.6.27.12 and 2.6.27.13
> >
> > Still on a 2.6.27.6 I got this on an NFS client while restarting the
> > NFS-server at the other end. Seems autofs/nfs releated.
> >
> >
> > [6367172.212954] ------------[ cut here ]------------
> > [6367172.213122] kernel BUG at net/sunrpc/rpcb_clnt.c:498!
>
> Already fixed in 2.6.28 by the following commit.
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=9a4bd29fe8f6d3f015fe1c8e5450eb62cfebfcc9
>
> You should probably also apply the following commit (also in 2.6.28),
> which fixes a memory leak in the same area.
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=96165e2b7c4e2c82a0b60c766d4a2036444c21a0
Thanks for letting me know, I'll queue them up.
greg k-h
prev parent reply other threads:[~2009-01-29 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090125004823.GA6711@kroah.com>
2009-01-28 12:58 ` Linux 2.6.27.13 Jesper Krogh
[not found] ` <4980565E.3000800-Q2TZfHgGEy4@public.gmane.org>
2009-01-28 19:33 ` Trond Myklebust
[not found] ` <1233171227.9785.28.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-01-29 0:37 ` Greg KH [this message]
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=20090129003712.GC23732@kroah.com \
--to=greg@kroah.com \
--cc=autofs-CPWUtch7KCBzeIdxy0IIJw@public.gmane.org \
--cc=gregkh@suse.de \
--cc=jesper-Q2TZfHgGEy4@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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