+ genhd-register-the-block_ext_major-blockdev.patch added to -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch titled
     genhd: register the BLOCK_EXT_MAJOR blockdev
has been added to the -mm tree.  Its filename is
     genhd-register-the-block_ext_major-blockdev.patch

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: genhd: register the BLOCK_EXT_MAJOR blockdev
From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>

We run into system boot failure with kernel 2.6.28-rc.  We found it on a
couple of machines, including T61 notebook, nehalem machine, and another
HPC NX6325 notebook.  All the machines use FedoraCore 8 or FedoraCore 9. 
With kernel prior to 2.6.28-rc, system boot doesn't fail.

I debug it and locate the root cause.  See
http://bugzilla.kernel.org/show_bug.cgi?id=11899
https://bugzilla.redhat.com/show_bug.cgi?id=471517

As a matter of fact, there are 2 bugs.

1) root=/dev/sda1, system boot randomly fails.  Mostly, boot for 5
   times and fails once.  nash has a bug.  Some of its functions misuse
   return value 0.  Sometimes, 0 means timeout and no uevent available. 
   Sometimes, 0 means nash gets an uevent, but the uevent isn't
   block-related (for exmaple, usb).  If by coincidence, kernel tells nash
   that uevents are available, but kernel also set timeout, nash might
   stops collecting other uevents in queue if current uevent isn't
   block-related.

   I work out a patch for nash to fix it. 
   http://bugzilla.kernel.org/attachment.cgi?id=18858

2) root=LABEL=/, system always can't boot.  initrd init reports
   switchroot fails.  Here is an executation branch of nash when booting:

    (1) nash read /sys/block/sda/dev; Assume major is 8 (on my desktop)

    (2) nash query /proc/devices with the major number; It found line  "8 sd";

    (3) nash use 'sd' to search its own probe table to find device
        (DISK) type for the device and add it to its own list;

    (4) Later on, it probes all devices in its list to get
        filesystem labels; scsi register "8 sd" always.

When major is 259, nash fails to find the device(DISK) type.  I enables
CONFIG_DEBUG_BLOCK_EXT_DEVT=y when compiling kernel, so 259 is picked up
for device /dev/sda1, which causes nash to fail to find device (DISK)
type.  To fixing issue 2), I create a patch for nash and another patch for
kernel.

http://bugzilla.kernel.org/attachment.cgi?id=18859
http://bugzilla.kernel.org/attachment.cgi?id=18837

This patch registers blkext, a new block device in proc/devices.

With 2 patches on nash and 1 patch on kernel, I boot my machines for
dozens of times without failure.

Signed-off-by Zhang Yanmin <yanmin.zhang@xxxxxxxxxxxxxxx>
Acked-by: Tejun Heo <tj@xxxxxxxxxx>
Cc: Jens Axboe <jens.axboe@xxxxxxxxxx>
Cc: "Rafael J. Wysocki" <rjw@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---

 block/genhd.c |    1 +
 1 file changed, 1 insertion(+)

diff -puN block/genhd.c~genhd-register-the-block_ext_major-blockdev block/genhd.c
--- a/block/genhd.c~genhd-register-the-block_ext_major-blockdev
+++ a/block/genhd.c
@@ -1028,6 +1028,7 @@ static int __init proc_genhd_init(void)
 {
 	proc_create("diskstats", 0, NULL, &proc_diskstats_operations);
 	proc_create("partitions", 0, NULL, &proc_partitions_operations);
+	register_blkdev(BLOCK_EXT_MAJOR, "blkext");
 	return 0;
 }
 module_init(proc_genhd_init);
_

Patches currently in -mm which might be from yanmin_zhang@xxxxxxxxxxxxxxx are

genhd-register-the-block_ext_major-blockdev.patch

--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Newbies FAQ]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux