linux-kernel - Boot failure with block/for-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Dec 2010 11:27:03 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Jens Axboe <axboe@...nel.dk>, Tejun Heo <htejun@...il.com>
Cc:	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Boot failure with block/for-next

Trying to test out the SCSI post merge tree, I've found it won't boot on
my SCSI test system.  The reason is a failure to read the partition
table of the root disc.  It just gives

sda: unable to read partition table

The other four discs in the system seem to read their partition tables
OK.

The obvious candidate is the partition code rework in block/for-next.
Simply reverting 

commit d2bf1b6723ed0eab378363649d15b7893bf14e91
Author: Tejun Heo <tj@...nel.org>
Date:   Wed Dec 8 20:57:36 2010 +0100

    block: move register_disk() and del_gendisk() to block/genhd.c

Doesn't fix the boot failure, so it's obviously something deeper.

James

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/