linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "'cel@kernel.org'" <cel@kernel.org>,
	 Hugh Dickins <hughd@google.com>,
	Christian Brauner <brauner@kernel.org>,
	 Al Viro <viro@zeniv.linux.org.uk>,
	 "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	 "linux-mm@kvack.org" <linux-mm@kvack.org>,
	 "yukuai3@huawei.com" <yukuai3@huawei.com>,
	"yangerkun@huaweicloud.com" <yangerkun@huaweicloud.com>,
	 Chuck Lever <chuck.lever@oracle.com>,
	 "stable@vger.kernel.org" <stable@vger.kernel.org>,
	 Jeff Layton <jlayton@kernel.org>,
	 Yang Erkun <yangerkun@huawei.com>
Subject: Re: [PATCH v5 1/5] libfs: Return ENOSPC when the directory offset range is exhausted
Date: Mon, 16 Dec 2024 13:39:06 +0000	[thread overview]
Message-ID: <mafs0o71b21dx.fsf@kernel.org> (raw)
In-Reply-To: <95d0b9296e3f48ffb79a1de0b95f4726@AcuMS.aculab.com> (David Laight's message of "Sun, 15 Dec 2024 19:35:57 +0000")

On Sun, Dec 15 2024, David Laight wrote:

> From: cel@kernel.org
>> Sent: 15 December 2024 18:58
>> 
>> From: Chuck Lever <chuck.lever@oracle.com>
>> 
>> Testing shows that the EBUSY error return from mtree_alloc_cyclic()
>> leaks into user space. The ERRORS section of "man creat(2)" says:
>> 
>> >	EBUSY	O_EXCL was specified in flags and pathname refers
>> >		to a block device that is in use by the system
>> >		(e.g., it is mounted).
>> 
>> ENOSPC is closer to what applications expect in this situation.
>> 
>> Note that the normal range of simple directory offset values is
>> 2..2^63, so hitting this error is going to be rare to impossible.
>> 
>> Fixes: 6faddda69f62 ("libfs: Add directory operations for stable offsets")
>> Cc: <stable@vger.kernel.org> # v6.9+
>> Reviewed-by: Jeff Layton <jlayton@kernel.org>
>> Reviewed-by: Yang Erkun <yangerkun@huawei.com>
>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>> ---
>>  fs/libfs.c | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>> 
>> diff --git a/fs/libfs.c b/fs/libfs.c
>> index 748ac5923154..f6d04c69f195 100644
>> --- a/fs/libfs.c
>> +++ b/fs/libfs.c
>> @@ -292,7 +292,9 @@ int simple_offset_add(struct offset_ctx *octx, struct dentry *dentry)
>> 
>>  	ret = mtree_alloc_cyclic(&octx->mt, &offset, dentry, DIR_OFFSET_MIN,
>>  				 LONG_MAX, &octx->next_offset, GFP_KERNEL);
>> -	if (ret < 0)
>> +	if (unlikely(ret == -EBUSY))
>> +		return -ENOSPC;
>> +	if (unlikely(ret < 0))
>>  		return ret;
>
> You've just added an extra comparison to a hot path.
> Doing:
> 	if (ret < 0)
> 		return ret == -EBUSY ? -ENOSPC : ret;
> would be better.

This also has two comparisons: one for ret < 0 and another for ret ==
-EBUSY. So I don't see a difference. I was curious to see if compilers
can somehow optimize one or the other, so I ran the two on godbolt and I
see no real difference between the two: https://godbolt.org/z/9Gav6b6Mf

-- 
Regards,
Pratyush Yadav


  reply	other threads:[~2024-12-16 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 18:58 [PATCH v5 0/5] Improve simple directory offset wrap behavior cel
2024-12-15 18:58 ` [PATCH v5 1/5] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-12-15 19:35   ` David Laight
2024-12-16 13:39     ` Pratyush Yadav [this message]
2024-12-16 13:51       ` Chuck Lever
2024-12-15 18:58 ` [PATCH v5 2/5] Revert "libfs: Add simple_offset_empty()" cel
2024-12-15 18:58 ` [PATCH v5 3/5] Revert "libfs: fix infinite directory reads for offset dir" cel
2024-12-15 18:58 ` [PATCH v5 4/5] libfs: Replace simple_offset end-of-directory detection cel
2024-12-15 18:58 ` [PATCH v5 5/5] libfs: Use d_children list to iterate simple_offset directories cel

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=mafs0o71b21dx.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=brauner@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=hughd@google.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yangerkun@huawei.com \
    --cc=yangerkun@huaweicloud.com \
    --cc=yukuai3@huawei.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