public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dongliang Mu <[email protected]>
To: Muchun Song <[email protected]>
Cc: Dongliang Mu <[email protected]>, Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	[email protected], LKML <[email protected]>
Subject: Re: [PATCH] fs: io_uring: remove NULL check before kfree
Date: Tue, 14 Jun 2022 17:29:18 +0800	[thread overview]
Message-ID: <CAD-N9QViX0sS+w_g4cL1kaZaRduWwY8ZkOhmLzRL83MP0CVqAw@mail.gmail.com> (raw)
In-Reply-To: <CAMZfGtWswvFRp8UmnETRENsq1WBx9QvG7A_v8Eq62aaNA96wMw@mail.gmail.com>

On Tue, Jun 14, 2022 at 5:26 PM Muchun Song <[email protected]> wrote:
>
> On Tue, Jun 14, 2022 at 5:14 PM Dongliang Mu <[email protected]> wrote:
> >
> > From: mudongliang <[email protected]>
> >
> > kfree can handle NULL pointer as its argument.
> > According to coccinelle isnullfree check, remove NULL check
> > before kfree operation.
> >
> > Signed-off-by: mudongliang <[email protected]>
> > ---
> >  fs/io_uring.c | 15 +++++----------
> >  1 file changed, 5 insertions(+), 10 deletions(-)
> >
> > diff --git a/fs/io_uring.c b/fs/io_uring.c
> > index 3aab4182fd89..bec47eae2a9b 100644
> > --- a/fs/io_uring.c
> > +++ b/fs/io_uring.c
> > @@ -3159,8 +3159,7 @@ static void io_free_batch_list(struct io_ring_ctx *ctx,
> >                         if ((req->flags & REQ_F_POLLED) && req->apoll) {
> >                                 struct async_poll *apoll = req->apoll;
> >
> > -                               if (apoll->double_poll)
> > -                                       kfree(apoll->double_poll);
> > +                               kfree(apoll->double_poll);
> >                                 list_add(&apoll->poll.wait.entry,
> >                                                 &ctx->apoll_cache);
> >                                 req->flags &= ~REQ_F_POLLED;
> > @@ -4499,8 +4498,7 @@ static int io_read(struct io_kiocb *req, unsigned int issue_flags)
> >         kiocb_done(req, ret, issue_flags);
> >  out_free:
> >         /* it's faster to check here then delegate to kfree */
>
> I am feeling you are not on the right way. See the comment
> here.

Thanks for your reply. I ignore them previously. Any method to make
coccicheck ignore such cases?

>
> Thanks.
>
> > -       if (iovec)
> > -               kfree(iovec);
> > +       kfree(iovec);
> >         return 0;
> >  }
> >
> > @@ -4602,8 +4600,7 @@ static int io_write(struct io_kiocb *req, unsigned int issue_flags)
> >         }
> >  out_free:
> >         /* it's reportedly faster than delegating the null check to kfree() */
>
> See here.
>
> > -       if (iovec)
> > -               kfree(iovec);
> > +       kfree(iovec);
> >         return ret;
> >  }
> >
> > @@ -6227,8 +6224,7 @@ static int io_sendmsg(struct io_kiocb *req, unsigned int issue_flags)
> >                 req_set_fail(req);
> >         }
> >         /* fast path, check for non-NULL to avoid function call */
>
> here.
>
> > -       if (kmsg->free_iov)
> > -               kfree(kmsg->free_iov);
> > +       kfree(kmsg->free_iov);
> >         req->flags &= ~REQ_F_NEED_CLEANUP;
> >         if (ret >= 0)
> >                 ret += sr->done_io;
> > @@ -6481,8 +6477,7 @@ static int io_recvmsg(struct io_kiocb *req, unsigned int issue_flags)
> >         }
> >
> >         /* fast path, check for non-NULL to avoid function call */
>
> And here.
>
> > -       if (kmsg->free_iov)
> > -               kfree(kmsg->free_iov);
> > +       kfree(kmsg->free_iov);
> >         req->flags &= ~REQ_F_NEED_CLEANUP;
> >         if (ret >= 0)
> >                 ret += sr->done_io;
> > --
> > 2.35.1
> >

      reply	other threads:[~2022-06-14  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14  9:13 [PATCH] fs: io_uring: remove NULL check before kfree Dongliang Mu
2022-06-14  9:26 ` Muchun Song
2022-06-14  9:29   ` Dongliang Mu [this message]

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=CAD-N9QViX0sS+w_g4cL1kaZaRduWwY8ZkOhmLzRL83MP0CVqAw@mail.gmail.com \
    [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