From: "Michael Evans" <mjevans1983@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Michael J. Evans" <mjevans1983@comcast.net>,
"Neil Brown" <neilb@suse.de>, "Ingo Molnar" <mingo@redhat.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch v2 1/1] md: Software Raid autodetect dev list not array
Date: Sun, 26 Aug 2007 08:58:06 -0700 [thread overview]
Message-ID: <4877c76c0708260858i51ddfd6csb69d3adf405245eb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708261453450.15614@fbirervta.pbzchgretzou.qr>
On 8/26/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Aug 26 2007 04:51, Michael J. Evans wrote:
> > {
> >- if (dev_cnt >= 0 && dev_cnt < 127)
> >- detected_devices[dev_cnt++] = dev;
> >+ struct detected_devices_node *node_detected_dev;
> >+ node_detected_dev = kzalloc(sizeof(*node_detected_dev), GFP_KERNEL);\
>
> What's the \ good for, besides escaping the newline
> that is ignored as whitespace anyway? :-)
>
I hadn't even noticed that, I suppose I mashed the key above enter at
some time. Removing from my local file.
> >@@ -5772,3 +5790,8 @@ static void autostart_arrays(int part)
> >- for (i = 0; i < dev_cnt; i++) {
> >- dev_t dev = detected_devices[i];
> >-
> >+ /* FIXME: max 'int' #DEFINEd somewhere? not 0x7FFFFFFF ? */
> >+ while (!list_empty(&all_detected_devices) && i_scanned < 0x7FFFFFFF) {
>
> I doubt someone really has _that_ many devices. Of course, to be on the
> safer side, make it an unsigned int. That way, people could put in about
> 0xFFFFFFFE devs (which is even less likely than 0x7FFFFFFF)
>
There is that, but I'm almost expecting someone to ask me to remove
both the ints and kprint statement. (I'd like them as part of some
kind of verbose startup that people would actually think to use
however.) Additionally a though occurred to me earlier, if there are
That many devices, the chance of a UUID namespace collision might
actually be realistic anyway. Though I'm not short sighted enough to
put it past anyone to have more then 32/64K possible block devices.
Anyone with that much cash today is probably buying hardware raid, but
who knows.
> >+ i_scanned++;
> >+ node_detected_dev = list_entry(all_detected_devices.next,
> >+ struct detected_devices_node, list);
> >+ list_del(&node_detected_dev->list);
> >+ dev = node_detected_dev->dev;
> >+ kfree(node_detected_dev);
>
> Jan
> --
>
next prev parent reply other threads:[~2007-08-26 15:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200708222058.45480.mjevans1983@comcast.net>
2007-08-24 3:37 ` [patch " Neil Brown
2007-08-24 5:50 ` Michael Evans
2007-08-26 11:51 ` [patch v2 " Michael J. Evans
2007-08-26 12:20 ` Michael Evans
2007-08-27 3:41 ` Kyle Moffett
2007-08-27 7:56 ` Michael Evans
2007-08-26 12:56 ` Jan Engelhardt
2007-08-26 15:58 ` Michael Evans [this message]
2007-08-26 16:56 ` Randy Dunlap
2007-08-26 19:18 ` Michael Evans
2007-08-27 22:16 ` [patch v3 " Michael J. Evans
2007-08-27 22:30 ` Randy Dunlap
2007-08-28 4:38 ` Michael J. Evans
2007-08-28 4:46 ` Randy Dunlap
2007-08-28 13:08 ` Michael Evans
2007-08-28 13:14 ` Jan Engelhardt
2007-08-28 13:26 ` Michael J. Evans
2007-08-28 13:24 ` Bill Davidsen
2007-08-28 13:32 ` Michael Evans
2007-08-28 16:15 ` Randy Dunlap
2007-08-28 17:10 ` Michael Evans
2007-08-28 17:22 ` Randy Dunlap
2007-08-28 19:11 ` Michael Evans
2007-08-28 19:16 ` Randy Dunlap
2007-08-29 8:06 ` [patch v5 " Michael J. Evans
2007-08-29 15:18 ` Randy Dunlap
2007-08-28 13:27 ` Michael J. Evans
2007-08-28 4:39 ` [patch v4 " Michael J. Evans
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=4877c76c0708260858i51ddfd6csb69d3adf405245eb@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjevans1983@comcast.net \
--cc=neilb@suse.de \
/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®