From: Nathan Chancellor <[email protected]>
To: Nick Desaulniers <[email protected]>
Cc: Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
Usama Arif <[email protected]>,
[email protected], [email protected],
[email protected]
Subject: Re: [PATCH] io_uring: Fix use of uninitialized ret in io_eventfd_register()
Date: Mon, 7 Feb 2022 12:36:31 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKwvOdnfQeY8sC0iET4hm-kgeFhurWf_jrh4=czBj17zQ5+x0Q@mail.gmail.com>
On Mon, Feb 07, 2022 at 11:32:03AM -0800, Nick Desaulniers wrote:
> On Mon, Feb 7, 2022 at 8:24 AM Nathan Chancellor <[email protected]> wrote:
> >
> > Clang warns:
> >
> > fs/io_uring.c:9396:9: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
> > return ret;
> > ^~~
> > fs/io_uring.c:9373:13: note: initialize the variable 'ret' to silence this warning
> > int fd, ret;
> > ^
> > = 0
> > 1 warning generated.
> >
> > Just return 0 directly and reduce the scope of ret to the if statement,
> > as that is the only place that it is used, which is how the function was
> > before the fixes commit.
> >
> > Fixes: 1a75fac9a0f9 ("io_uring: avoid ring quiesce while registering/unregistering eventfd")
>
> Did SHA's change? In linux-next, I see:
> commit b77e315a9644 ("io_uring: avoid ring quiesce while
> registering/unregistering eventfd")
> otherwise LGTM
Yes, this is against Jens' latest for-5.18/io_uring branch, which was
rebased after next-20220207 was released.
https://git.kernel.dk/cgit/linux-block/log/?h=for-5.18/io_uring
Cheers,
Nathan
> > Link: https://github.com/ClangBuiltLinux/linux/issues/1579
> > Signed-off-by: Nathan Chancellor <[email protected]>
> > ---
> > fs/io_uring.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/io_uring.c b/fs/io_uring.c
> > index 5479f0607430..7ef04bb66da1 100644
> > --- a/fs/io_uring.c
> > +++ b/fs/io_uring.c
> > @@ -9370,7 +9370,7 @@ static int io_eventfd_register(struct io_ring_ctx *ctx, void __user *arg,
> > {
> > struct io_ev_fd *ev_fd;
> > __s32 __user *fds = arg;
> > - int fd, ret;
> > + int fd;
> >
> > ev_fd = rcu_dereference_protected(ctx->io_ev_fd,
> > lockdep_is_held(&ctx->uring_lock));
> > @@ -9386,14 +9386,14 @@ static int io_eventfd_register(struct io_ring_ctx *ctx, void __user *arg,
> >
> > ev_fd->cq_ev_fd = eventfd_ctx_fdget(fd);
> > if (IS_ERR(ev_fd->cq_ev_fd)) {
> > - ret = PTR_ERR(ev_fd->cq_ev_fd);
> > + int ret = PTR_ERR(ev_fd->cq_ev_fd);
> > kfree(ev_fd);
> > return ret;
> > }
> > ev_fd->eventfd_async = eventfd_async;
> >
> > rcu_assign_pointer(ctx->io_ev_fd, ev_fd);
> > - return ret;
> > + return 0;
> > }
> >
> > static void io_eventfd_put(struct rcu_head *rcu)
> >
> > base-commit: 88a0394bc27de2dd8a8715970f289c5627052532
> > --
> > 2.35.1
> >
> >
>
>
> --
> Thanks,
> ~Nick Desaulniers
next prev parent reply other threads:[~2022-02-07 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 16:24 [PATCH] io_uring: Fix use of uninitialized ret in io_eventfd_register() Nathan Chancellor
2022-02-07 19:32 ` Nick Desaulniers
2022-02-07 19:36 ` Nathan Chancellor [this message]
2022-02-07 19:38 ` Nick Desaulniers
2022-02-08 13:37 ` [External] " Usama Arif
2022-02-08 13:58 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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