linux-kernel - Re: Linux 3.7-rc8

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]

Message-ID: <CA+55aFyAvpCKPWV9Mh34aV6Q4DRjATQky939vYaPBfx6+65Nxw@mail.gmail.com>
Date:	Mon, 3 Dec 2012 15:07:09 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Tony Luck <tony.luck@...el.com>
Cc:	Romain Francoise <romain@...bokech.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.7-rc8

On Mon, Dec 3, 2012 at 2:44 PM, Tony Luck <tony.luck@...el.com> wrote:
>> Just for info, can you add a "WARN_ON_ONCE()" to handle_bad_sector()
>> just so that I see which particular path your kvm load triggers.
>
> On native ia64 (with SLES11 userspace) I see:

Interesting. I knew about the possibility of this, and had actually
*tried* to trigger this with the regular read() system call. But
couldn't, so I had assumed that it was some special path (ie
O_DIRECT). But it's just the regular read-ahead.

I guess I need to try harder. I'm guessing that there's a 4kB
filesystem there, and the block device size isn't 4kB-aligned or
something.

              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/