From: Davidlohr Bueso <dave@gnu.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] jbd: Remove redundant NULL check upon kfree()
Date: Wed, 11 Aug 2010 09:11:37 -0400 [thread overview]
Message-ID: <1281532297.2067.8.camel@cowboy> (raw)
In-Reply-To: <alpine.LRH.2.00.1008111505420.2372@twin.jikos.cz>
On Wed, 2010-08-11 at 15:06 +0200, Jiri Kosina wrote:
> On Wed, 11 Aug 2010, Davidlohr Bueso wrote:
>
> > jbd: Remove redundant NULL check upon kfree().
> >
> > Signed-off-by: Davidlohr Bueso <dave@gnu.org>
> > ---
> > fs/jbd/transaction.c | 3 +--
> > 1 files changed, 1 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/jbd/transaction.c b/fs/jbd/transaction.c
> > index 5ae71e7..5e98130 100644
> > --- a/fs/jbd/transaction.c
> > +++ b/fs/jbd/transaction.c
> > @@ -232,8 +232,7 @@ repeat_locked:
> >
> > lock_map_acquire(&handle->h_lockdep_map);
> > out:
> > - if (unlikely(new_transaction)) /* It's usually NULL */
> > - kfree(new_transaction);
> > + kfree(new_transaction);
>
> This doesn't seem entirely redundant, as it is optimized (via the
> unlikely() hint) for the opposite case than what kfree() is optimized for
> (kfree() assumes that the pointer is likely non-NULL, while the code above
> assumes that the pointer si likely NULL).
>
Ok, makes sense. I was a bit doubtful about the unlikely(), thanks for
the review.
Davidlohr
prev parent reply other threads:[~2010-08-11 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 13:00 [PATCH] jbd: Remove redundant NULL check upon kfree() Davidlohr Bueso
2010-08-11 13:06 ` Jiri Kosina
2010-08-11 13:11 ` Davidlohr Bueso [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=1281532297.2067.8.camel@cowboy \
--to=dave@gnu.org \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.