linux-kernel - Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 1 Feb 2007 15:47:05 -0700
From:	"Eric D. Mudama" <edmudama@...il.com>
To:	"Andrew Morton" <akpm@...l.org>
Cc:	TJ <linux@...orld.net>,
	"OGAWA Hirofumi" <hirofumi@...l.parknet.co.jp>,
	"Neil Brown" <neilb@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

On 2/1/07, Andrew Morton <akpm@...l.org> wrote:
> Also, from reading the replies I think we'd like to see some more
> explanation of why this is necessary: are you really really sure that those
> disks were incorrectly handling illegal sector numbers?  Knowing the IBM
> and Maxtor model numbers might be useful.

I'd like to know the model numbers (and firmware revisions) too.

The drive knows how many LBAs it has, and making sure the span of the
command is within the valid LBA space is one of the first things
checked.

Another possibility of for clunking is if the drive is damaged and
cannot track follow in a region, the drive will go to the latch and
push off repeatedly attempting to reacquire servo information.  That
can be scary sounding if you haven't heard it before.

Not saying the bug is impossible, but I'd like to know more.

--eric
-
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/