From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Jeff Layton <jlayton@redhat.com>,
Ricky Ng-Adam <rngadam@lophilo.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"neilb@suse.de" <neilb@suse.de>
Subject: Re: WARNING: at linux/fs/inode.c:280 drop_nlink
Date: Thu, 13 Dec 2012 21:07:53 +0000 [thread overview]
Message-ID: <20121213210753.GQ4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA91192A83F@SACEXCMBX04-PRD.hq.netapp.com>
On Thu, Dec 13, 2012 at 02:45:18PM +0000, Myklebust, Trond wrote:
> You mean aside from the fact that sb->s_remove_count remains a racy
> piece of crap that serves no good purpose for NFS, and yet will continue
> to give us grief?
As opposed to scanning the list of opened files?
next prev parent reply other threads:[~2012-12-13 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 12:19 WARNING: at linux/fs/inode.c:280 drop_nlink Ricky Ng-Adam
2012-11-12 14:52 ` Jeff Layton
2012-12-13 11:31 ` Jeff Layton
2012-12-13 14:45 ` Myklebust, Trond
2012-12-13 21:07 ` Al Viro [this message]
2012-12-13 21:22 ` Myklebust, Trond
2012-12-14 3:06 ` Jeff Layton
2012-12-14 3:22 ` Myklebust, Trond
2012-12-14 12:51 ` Jeff Layton
2012-12-14 18:22 ` Myklebust, Trond
2012-12-17 13:08 ` Jeff Layton
2012-12-17 15:14 ` Myklebust, Trond
2012-12-17 15:23 ` Jeff Layton
2012-12-14 21:53 ` [PATCH 1/2] NFS: Ensure that we always drop inodes that have been marked as stale Trond Myklebust
2012-12-14 21:53 ` [PATCH 2/2] NFS: Fix calls to drop_nlink() Trond Myklebust
2012-12-17 12:47 ` [PATCH 1/2] NFS: Ensure that we always drop inodes that have been marked as stale Jeff Layton
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=20121213210753.GQ4939@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Trond.Myklebust@netapp.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rngadam@lophilo.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.