linux-kernel - Re: What's in libata-dev.git

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 11 Sep 2006 09:04:24 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Jens Axboe <axboe@...e.de>
cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, Jeff Garzik <jeff@...zik.org>,
	Sergei Shtylyov <sshtylyov@...mvista.com>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...l.org>
Subject: Re: What's in libata-dev.git

On Mon, 11 Sep 2006, Jens Axboe wrote:
> 
> So this is a confirmed, broken case? Why has no one complained for 2.4
> and 2.6?

Oh, I didn't even notice that we do that by default already. That's a bit 
scary - I remember people having their disks trashed.

Maybe the broken disks are old enough to not be an issue any more, or 
maybe something else makes it effectively impossible to trigger in 
practice?

You do need to get 32 pages of contiguous IO for it to happen, and while I 
don't see anything else that would limit it, maybe there is something that 
does? (Some other limiter like max_phys_segments might, but that 
particular one defaults to much more than 32)

Of course, we do hopefully handle requests that fail a lot more 
gracefully these days, so if the drive says it didn't do it, maybe we just 
fix it up properly, in a way we didn't use to.. Ie we may have fixed the 
thing that caused corruption just by fixing something else ;)

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