From: Weston Andros Adamson <dros@primarydata.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Peng Tao <tao.peng@primarydata.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
linux-nfs list <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: WARNING at fs/nfs/write.c:743 nfs_inode_remove_request with -rc6
Date: Thu, 25 Sep 2014 13:27:35 -0400 [thread overview]
Message-ID: <78B8153D-59B7-4DBE-8472-D83338F04338@primarydata.com> (raw)
In-Reply-To: <20140925171545.GR20043@arm.com>
On Sep 25, 2014, at 1:15 PM, Will Deacon <will.deacon@arm.com> wrote:
> Hi Andros,
>
> On Tue, Sep 23, 2014 at 04:25:58PM +0100, Will Deacon wrote:
>> On Tue, Sep 23, 2014 at 04:08:36PM +0100, Weston Andros Adamson wrote:
>>> On Sep 23, 2014, at 11:02 AM, Weston Andros Adamson <dros@primarydata.com> wrote:
>>>> Wait a second - the whole point of this extra reference (that the
>>>> WARN_ON_ONCE is related to) is to handle the pass off to commit lists.
>>>>
>>>> Maybe I’m just doing the wrong thing here with NFSv2!
>>>>
>>>> More soon.
>>>
>>> Actually, can you see if this is reproducible with NFSv3?
>>
>> Just tried that, and I'm unable to trigger the problem with NFSv3.
>
> Any more ideas? I can run with NFSv3 instead, but it's a shame to leave
> v2 broken.
Hi Will,
I do plan on looking at this more very soon, but since it’s v2 only and just warning
(and not crashing anything) it didn’t jump to the top of my list. It is only printing the
warnings, right? That’s no reason to switch things up ;)
It might be interesting to get some rpcdebug output around the time of the warning,
but I’m not sure it will be useful.
Since I cannot reproduce this, my next step is to inspect the code with an NFSv2
with 64k pages setup in mind.
-dros
next prev parent reply other threads:[~2014-09-25 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 13:03 WARNING at fs/nfs/write.c:743 nfs_inode_remove_request with -rc6 Will Deacon
2014-09-23 13:33 ` Weston Andros Adamson
2014-09-23 13:59 ` Will Deacon
2014-09-23 14:53 ` Will Deacon
2014-09-23 14:59 ` Weston Andros Adamson
2014-09-23 15:02 ` Weston Andros Adamson
2014-09-23 15:08 ` Weston Andros Adamson
2014-09-23 15:25 ` Will Deacon
2014-09-25 17:15 ` Will Deacon
2014-09-25 17:27 ` Weston Andros Adamson [this message]
2014-10-11 13:32 ` Weston Andros Adamson
2014-10-20 13:57 ` Will Deacon
2014-10-31 14:49 ` Weston Andros Adamson
2014-10-31 14:55 ` Will Deacon
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=78B8153D-59B7-4DBE-8472-D83338F04338@primarydata.com \
--to=dros@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tao.peng@primarydata.com \
--cc=trond.myklebust@primarydata.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox