From: NeilBrown <neilb@suse.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: "J. Bruce Fields" <bfields@redhat.com>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] reconnect_one(): fix a missing error code
Date: Thu, 15 Jun 2017 07:54:57 +1000 [thread overview]
Message-ID: <87lgou6xqm.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20170614203414.GC32208@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
On Wed, Jun 14 2017, J. Bruce Fields wrote:
> On Wed, Jun 14, 2017 at 12:30:02PM +0300, Dan Carpenter wrote:
>> I found this bug by reviewing places where we do ERR_PTR(0) (which is
>> NULL).
>>
>> We used to return an error pointer if lookup_one_len() failed but we
>> moved this code into a helper function and accidentally removed that.
>> NULL is a valid return for this function but it's not what we intended.
>>
>> Fixes: bbf7a8a3562f ("exportfs: move most of reconnect_path to helper function")
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> ACK. Agreed that the current code is wrong, and that this is the
> correct fix.
>
> What I don't quite understand yet is what the impact of the bug would
> be.
>
It is interesting that reconnect_path() handles the possibility of
reconnect_one() returning NULL, even though it will only do that if this
"bug" is triggered.
When that happens, the target_dir (a descendent of dentry) gets its
DCACHE_DISCONNECTED flag cleared.
The bug can presumably only be triggered by a race.
We look through a directory to find the name for an inode
(exportfs_get_name), then try to look up that name and it doesn't exist.
So presumably if you lose the race, some dentry will get
DCACHE_DISCONNECTED cleared, even though it is still disconnected.
This breaks a contract and can cause weirdness in dcache operations.
If the lookup_one_len_unlocked() fails, we should probably retry, at
least once. But if we do decide to give up, we shouldn't assume it all
worked.
So I suggest:
- the fix as provided by Dan, plus
- remove "if (!parent) break;" from reconnect_path(), plus
- maybe retry the get_name/lookup_one operation once if the first
attempt fails.
NeilBrown
> --b.
>
>>
>> diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
>> index 329a5d103846..451237745689 100644
>> --- a/fs/exportfs/expfs.c
>> +++ b/fs/exportfs/expfs.c
>> @@ -147,6 +147,7 @@ static struct dentry *reconnect_one(struct vfsmount *mnt,
>> tmp = lookup_one_len_unlocked(nbuf, parent, strlen(nbuf));
>> if (IS_ERR(tmp)) {
>> dprintk("%s: lookup failed: %d\n", __func__, PTR_ERR(tmp));
>> + err = PTR_ERR(tmp);
>> goto out_err;
>> }
>> if (tmp != dentry) {
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-14 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 9:30 Dan Carpenter
2017-06-14 20:34 ` J. Bruce Fields
2017-06-14 21:54 ` NeilBrown [this message]
2017-06-15 9:26 ` Dan Carpenter
2017-06-15 21:40 ` J. Bruce Fields
2017-06-15 22:28 ` NeilBrown
2017-06-16 13:50 ` 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=87lgou6xqm.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®