mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
Cc: Tejun Heo <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix use-after-free of q->root_blkg and q->root_rl.blkg
Date: Thu, 18 Oct 2012 09:31:49 -0400	[thread overview]
Message-ID: <20121018133149.GA18147@redhat.com> (raw)
In-Reply-To: <507F6FE2.3030303@ce.jp.nec.com>

On Thu, Oct 18, 2012 at 11:56:34AM +0900, Jun'ichi Nomura wrote:

[..]
> >>>         if (ent == &q->root_blkg->q_node)
> >>
> >> So ent is not &q->root_blkg->q_node.
> > 
> > If q->root_blkg is NULL, will it not lead to NULL pointer dereference.
> > (q->root_blkg->q_node).
> 
> It's not dereferenced.

Ok. We are taking address of root_blkg->q_node so even if root_blkg=NULL,
address is just offset from null. Little subtle for me. :-)

> 
> >>>                 ent = ent->next;
> >>>         if (ent == &q->blkg_list)
> >>>                 return NULL;
> >>
> >> And we return NULL here.
> >>
> >> Ah, yes. You are correct.
> >> We can do without the above hunk.
> > 
> > I would rather prefer to check for this boundary condition early and
> > return instead of letting it fall through all these conditions and
> > then figure out yes we have no next rl. IMO, code becomes easier to
> > understand if nothing else. Otherwise one needs a step by step 
> > explanation as above to show that case of q->root_blkg is covered.
> 
> I have same opinion as yours that it's good for readability.


Tejun, for the sake of readability, are you fine with keeping the original
check and original patch which I had acked.

Thanks
Vivek

  reply	other threads:[~2012-10-18 13:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  5:11 Jun'ichi Nomura
2012-10-10 15:59 ` Vivek Goyal
2012-10-11  1:31   ` Jun'ichi Nomura
2012-10-11 18:55     ` Vivek Goyal
2012-10-16 23:20     ` Tejun Heo
2012-10-17  0:02       ` Jun'ichi Nomura
2012-10-17  8:45         ` [PATCH] blkcg: " Jun'ichi Nomura
2012-10-18 21:21           ` Tejun Heo
2012-10-22 18:43           ` Jens Axboe
2012-10-17 13:47         ` [PATCH] " Vivek Goyal
2012-10-18  2:56           ` Jun'ichi Nomura
2012-10-18 13:31             ` Vivek Goyal [this message]
2012-10-18 21:20               ` Tejun Heo
2012-10-19 14:53                 ` Vivek Goyal
2012-10-22  0:55                   ` Jun'ichi Nomura
2012-10-22  1:15                 ` [PATCH] blkcg: stop iteration early if root_rl is the only request list Jun'ichi Nomura
2012-10-22 15:31                   ` Vivek Goyal
2012-10-22 18:43                   ` 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 \
    --in-reply-to=20121018133149.GA18147@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome