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]

Date:	Mon, 3 Dec 2012 15:14:25 -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 3:07 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> 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.

Anyway, to clarify: the printk's are harmless, since the IO past the
end of the device is just error'ed out, and always has been.  Which is
why I was considering just removing them.

At the same time, those printk's have historically been useful for
finding unrelated bugs (ie filesystem corruption etc that causes
insane accesses) and there is the issue of the difference between EOF
and EIO return values, so I've been trying to trigger this for normal
read/writes to make sure that there wasn't anything going on there.
All of the paths I've looked at seem to look at the inode size, but
clearly I missed some.

I bet it's read-ahead together with something particular that allows
you to trigger it.

              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/