From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
Dan Aloni <dan@kernelim.com>
Subject: Re: [PATCH v2] nfs: fix kernel warning when removing proc entry
Date: Mon, 8 Sep 2014 13:26:20 -0700 [thread overview]
Message-ID: <CAADnVQLTRq=GyCYFXUWGiRm=1hgi4s4kA4SS5rtVSCHHud1uTg@mail.gmail.com> (raw)
In-Reply-To: <20140908185039.GA1616@whiteoak.sf.office.twttr.net>
On Mon, Sep 8, 2014 at 11:50 AM, Matt Mullins <mmullins@twopensource.com> wrote:
> On Tue, Aug 19, 2014 at 09:20:38PM -0700, Eric W. Biederman wrote:
>> I have applied this patch and will push it to Linus after it has a
>> little bit to sit in linux-next.
what's the status of this patch?
It's rc4 already and I keep seeing it every boot:
[ 7.730034] WARNING: CPU: 3 PID: 103 at ../fs/proc/generic.c:521
remove_proc_entry+0x1a4/0x1b0()
[ 7.730036] remove_proc_entry: removing non-empty directory
'fs/nfsfs', leaking at least 'volumes'
[ 7.730037] Modules linked in: ...
[ 7.730063] CPU: 3 PID: 103 Comm: kworker/u8:15 Not tainted 3.17.0-rc4+ #196
prev parent reply other threads:[~2014-09-08 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 19:36 [PATCH v2] nfs: fix kernel warning when removing proc entry Cong Wang
2014-08-20 4:20 ` Eric W. Biederman
[not found] ` <alpine.DEB.2.19.4.1408192222470.2758@trent.utfs.org>
2014-08-20 23:16 ` Trond Myklebust
2014-08-20 23:27 ` Trond Myklebust
2014-08-28 1:41 ` Al Viro
2014-09-08 23:54 ` Trond Myklebust
2014-09-09 2:59 ` Cong Wang
2014-09-08 18:50 ` Matt Mullins
2014-09-08 20:26 ` Alexei Starovoitov [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='CAADnVQLTRq=GyCYFXUWGiRm=1hgi4s4kA4SS5rtVSCHHud1uTg@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=dan@kernelim.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=xiyou.wangcong@gmail.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 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.