From: Jeff Layton <jlayton@kernel.org>
To: cel@kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, Hugh Dickens <hughd@google.com>
Cc: yukuai3@huawei.com, yangerkun@huaweicloud.com,
Chuck Lever <chuck.lever@oracle.com>,
stable@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] libfs: Return ENOSPC when the directory offset range is exhausted
Date: Mon, 18 Nov 2024 14:55:48 -0500 [thread overview]
Message-ID: <94c96fd93a065323c2520ca399612e2d6c353f49.camel@kernel.org> (raw)
In-Reply-To: <20241117213206.1636438-2-cel@kernel.org>
On Sun, 2024-11-17 at 16:32 -0500, cel@kernel.org wrote:
> 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+
> 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 46966fd8bcf9..bf67954b525b 100644
> --- a/fs/libfs.c
> +++ b/fs/libfs.c
> @@ -288,7 +288,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;
>
> offset_set(dentry, offset);
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-11-18 19:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 21:32 [RFC PATCH 0/2] Improve simple directory offset wrap behavior cel
2024-11-17 21:32 ` [RFC PATCH 1/2] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-11-18 19:55 ` Jeff Layton [this message]
2024-11-17 21:32 ` [RFC PATCH 2/2] libfs: Improve behavior when directory offset values wrap cel
2024-11-18 20:00 ` Jeff Layton
2024-11-18 20:58 ` Chuck Lever
2024-11-20 8:59 ` Christian Brauner
2024-11-20 15:05 ` Chuck Lever
2024-11-21 8:34 ` Christian Brauner
2024-11-21 14:54 ` Chuck Lever III
2024-11-21 21:18 ` Hugh Dickins
2024-11-21 21:29 ` Chuck Lever
2024-11-22 8:49 ` Amir Goldstein
2024-11-22 14:24 ` Chuck Lever III
2024-12-04 21:05 ` Chuck Lever
2024-11-22 12:57 ` Christian Brauner
2024-11-24 21:28 ` Chuck Lever III
2024-11-20 9:01 ` [RFC PATCH 0/2] Improve simple directory offset wrap behavior Christian Brauner
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=94c96fd93a065323c2520ca399612e2d6c353f49.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--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