From: Joel Becker <jlbec@evilplan.org>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH 3/4] configfs: Correct error value returned by API config_item_set_name()
Date: Tue, 8 Apr 2025 15:26:09 -0700 [thread overview]
Message-ID: <Z_WigcRfU7iWnTVv@google.com> (raw)
In-Reply-To: <20250408-fix_configfs-v1-3-5a4c88805df7@quicinc.com>
On Tue, Apr 08, 2025 at 09:26:09PM +0800, Zijun Hu wrote:
> From: Zijun Hu <quic_zijuhu@quicinc.com>
>
> kvasprintf() failure is often caused by memory allocation which has error
> code -ENOMEM, but config_item_set_name() returns -EFAULT for the failure.
>
> Fix by returning -ENOMEM instead of -EFAULT for the failure.
The original code would return -ENOMEM on allocation failure before
calling vsnprintf(). The -EFAULT was because vsnprintf() failed.
This changed in 707c62352909a when vsnprintf() was changed to
kvasprintf(). Since kvasprintf() only really fails on -ENOMEM, the
error code should have been updated at the time.
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
Reviewed-by: Joel Becker <jlbec@evilplan.org>
> ---
> fs/configfs/item.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/configfs/item.c b/fs/configfs/item.c
> index 254170a82aa337d95cbfbdf1a2db1023db3a2907..c378b5cbf87d28387a509c3cabb93eccfb520c9c 100644
> --- a/fs/configfs/item.c
> +++ b/fs/configfs/item.c
> @@ -66,7 +66,7 @@ int config_item_set_name(struct config_item *item, const char *fmt, ...)
> name = kvasprintf(GFP_KERNEL, fmt, args);
> va_end(args);
> if (!name)
> - return -EFAULT;
> + return -ENOMEM;
> }
>
> /* Free the old name, if necessary. */
>
> --
> 2.34.1
>
--
Life's Little Instruction Book #274
"Leave everything a little better than you found it."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2025-04-08 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 13:26 [PATCH 0/4] configfs: fix bugs Zijun Hu
2025-04-08 13:26 ` [PATCH 1/4] configfs: Delete semicolon from macro type_print() definition Zijun Hu
2025-04-08 22:12 ` Joel Becker
2025-04-17 14:38 ` Breno Leitao
2025-04-17 14:47 ` Zijun Hu
2025-04-08 13:26 ` [PATCH 2/4] configfs: Do not override creating attribute file failure in populate_attrs() Zijun Hu
2025-04-08 22:14 ` Joel Becker
2025-04-08 13:26 ` [PATCH 3/4] configfs: Correct error value returned by API config_item_set_name() Zijun Hu
2025-04-08 22:26 ` Joel Becker [this message]
2025-04-08 13:26 ` [PATCH 4/4] configfs: Correct condition for returning -EEXIST in configfs_symlink() Zijun Hu
2025-04-08 22:49 ` Joel Becker
2025-04-10 1:17 ` Zijun Hu
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=Z_WigcRfU7iWnTVv@google.com \
--to=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=quic_zijuhu@quicinc.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zijun_hu@icloud.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