From: Greg KH <greg@kroah.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-nfs@vger.kernel.org, Neil Brown <neilb@suse.de>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
akpm@linux-foundation.org, stable@kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: [stable] [105/105] nfsd4: fix oops on lock failure
Date: Mon, 18 Apr 2011 11:21:23 -0700 [thread overview]
Message-ID: <20110418182123.GA12086@kroah.com> (raw)
In-Reply-To: <20110418171640.GJ20935@pad.home.fieldses.org>
On Mon, Apr 18, 2011 at 01:16:43PM -0400, J. Bruce Fields wrote:
> On Mon, Apr 18, 2011 at 09:59:26AM -0700, Linus Torvalds wrote:
> > On Mon, Apr 18, 2011 at 9:39 AM, OGAWA Hirofumi
> > <hirofumi@mail.parknet.co.jp> wrote:
> > >
> > > For now, I feel this explain filp leak on my system. the leak is
> > > increased slowly (filp, cred_jar, and no nfs* slabs), and leak is on
> > > nfs server side.
> > >
> > > I'll start test of this patch, and see what happens.
> >
> > Can somebody ping/remind me when that is verified - preferably about
> > _both_ patches, even if it turns out that the first one by Ogawa
> > wasn't the one that caused the problem?
> >
> > Or can I just assume that the fix will be in Bruce's pull requests some day?
>
> I'll send a pull request when it's sorted out, thanks.
Please tag it for stable as well so I know to pick it up.
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-18 18:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110412143559.186613198@clark.kroah.org>
[not found] ` <87pqokx6lr.fsf@devron.myhome.or.jp>
2011-04-17 16:10 ` [105/105] nfsd4: fix oops on lock failure Linus Torvalds
2011-04-18 15:32 ` J. Bruce Fields
2011-04-18 15:42 ` J. Bruce Fields
2011-04-18 16:08 ` OGAWA Hirofumi
2011-04-18 16:10 ` OGAWA Hirofumi
2011-04-18 16:39 ` OGAWA Hirofumi
2011-04-18 16:59 ` Linus Torvalds
2011-04-18 17:16 ` J. Bruce Fields
2011-04-18 18:21 ` Greg KH [this message]
2011-04-18 21:12 ` OGAWA Hirofumi
2011-04-19 8:21 ` OGAWA Hirofumi
2011-04-19 20:43 ` J. Bruce Fields
2011-04-19 21:17 ` OGAWA Hirofumi
[not found] ` <87aafmgcvk.fsf-x/W9pkDDSe1TgC2z9Sl/nXf5DAMn2ifp@public.gmane.org>
2011-04-19 21:33 ` J. Bruce Fields
2011-04-20 23:23 ` nfsd bugfixes for 2.6.39 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=20110418182123.GA12086@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bfields@redhat.com \
--cc=gregkh@suse.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).