From: Logan Gunthorpe <logang@deltatee.com>
To: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>, gregkh@linuxfoundation.org
Cc: axboe@kernel.dk, jlayton@poochiereds.net, bfields@fieldses.org,
linux-kernel@vger.kernel.org
Subject: Re: Change in register_blkdev() behavior
Date: Thu, 1 Feb 2018 18:10:50 -0700 [thread overview]
Message-ID: <c4e3aba6-74ac-f19f-47eb-45484e18630a@deltatee.com> (raw)
In-Reply-To: <e23b4d8f-9391-d214-e370-548244339cfb@csail.mit.edu>
On 01/02/18 05:23 PM, Srivatsa S. Bhat wrote:
> static int find_dynamic_major(void)
> {
> int i;
> struct char_device_struct *cd;
>
> for (i = ARRAY_SIZE(chrdevs)-1; i > CHRDEV_MAJOR_DYN_END; i--) {
> ^^^^
> As far as I can see, _DYN_END is inclusive, so shouldn't this be >= ?
Yes, it looks like _DYN_END should have been inclusive based on the way
I documented it.
>
> for (cd = chrdevs[major_to_index(i)]; cd; cd = cd->next)
> if (cd->major == i)
> break;
>
> if (cd == NULL || cd->major != i)
> ^^^^^^^^
> It seems that this latter condition is unnecessary, as it will never be
> true. (We'll reach here only if cd == NULL or cd->major == i).
Not quite. chrdevs[] may contain majors that also hit on the hash but
don't equal 'i'. So the for loop will iterate through all hashes
matching 'i' and if there is one or more and they all don't match 'i',
it will fall through the loop and cd will be set to something non-null
and not equal to i.
Thanks for the review!
Logan
next prev parent reply other threads:[~2018-02-02 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 0:56 Srivatsa S. Bhat
2018-01-31 1:26 ` Logan Gunthorpe
2018-02-02 0:23 ` Srivatsa S. Bhat
2018-02-02 1:10 ` Logan Gunthorpe [this message]
2018-02-02 2:17 ` Srivatsa S. Bhat
2018-02-02 6:12 ` Logan Gunthorpe
2018-01-31 14:24 ` Greg KH
2018-02-02 0:25 ` Srivatsa S. Bhat
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=c4e3aba6-74ac-f19f-47eb-45484e18630a@deltatee.com \
--to=logang@deltatee.com \
--cc=axboe@kernel.dk \
--cc=bfields@fieldses.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=srivatsa@csail.mit.edu \
/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
all inboxes | Powered by JetHome®