linux-kernel - Re: 2.6.20-mm1 - Oops using Minix 3 file system

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:	Sat, 17 Feb 2007 19:49:50 +0100
From:	"Daniel Aragonés" <danarag@...il.com>
To:	"Cédric Augonnet" <cedric.augonnet@...il.com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Cedric.augonnet@...-lyon.org
Subject: Re: 2.6.20-mm1 - Oops using Minix 3 file system

On 2/17/07, Cédric Augonnet <cedric.augonnet@...il.com> wrote:

>
> Well i actually do access to this partition, i can edit it and use it,
> this on Linux. Sorry if this is not clear.
>

Here is the point, I think. I'm afraid that you don't really access
any *real* partition. If it were so, that partition would have an
identifying *device* name. You access something within an image for an
emulating program that you interpret as a partition but not the
kernel. So it cannot access the superblock of it in its buffer and
recover bh->b_size to go on properly. It recovers something else. And
this triggers the oops.

Regards,

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