linux-kernel - Re: V3 minixfs bug

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

Message-ID: <20090702222704.15305c09@lxorguk.ukuu.org.uk>
Date:	Thu, 2 Jul 2009 22:27:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Doug Graham" <dgraham@...tel.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: V3 minixfs bug

On Thu, 02 Jul 2009 17:13:42 -0400
"Doug Graham" <dgraham@...tel.com> wrote:

> Is anybody interested in bugs in the minixfs V3 support that probably
> only turn up on big-endian machines, or on filesystems with more than
> 64K inodes?

If you've found them then yes.

> The problem is that that there are a few places (three that I've found)
> where the "inode" field of a minix_dir_entry is used without checking
> first to see if the dirent is really a minix3_dir_entry.  The inode number
> in a V1/V2 dirent is 16 bits, whereas that in a V3 dirent is 32 bits.  
> Accessing
> it as a 16 bit field when it really should be accessed as a 32 bit field
> probably kinda sorta works on a little-endian machine, but leads to some
> rather odd behaviour on big-endian machines.
> 
> Here's a patch:

The one thing this needs for application is a Signed-off-by: line (see
Documentation/SubmittingPatches). 

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