linux-kernel - Re: [PATCH] [UFS] fs/ufs/super.c misreads the file system state

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: <alpine.LFD.0.999.0709201804050.17093@enigma.security.iitk.ac.in>
Date:	Thu, 20 Sep 2007 18:09:28 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	Leonid Kalev <lion@...ra.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, dushistov@...l.ru
Subject: Re: [PATCH] [UFS] fs/ufs/super.c misreads the file system state



On Wed, 19 Sep 2007, Leonid Kalev wrote:
> 
> ufs_get_fs_state() needs the file system type to read the state from the
> correct place in the superblock. It takes the type from UFS_SB(sb)->s_flags,
> but that value is stored after the first call to ufs_get_fs_state(). The patch
> below moves the assignment of s_flags up, before the first call to
> ufs_get_fs_state().
> 
> The patch is against linux-2.6.23-rc6-git7, but it applies (with offset) to
> 2.6.22 and to earlier versions as well. It has been tested on the Solaris
> flavor of UFS (ufstype=sunx86) - with this change, the file system can be used
> in read-write mode.

The same fix is already in 2.6.23-rc6-mm1 (don't know if it's lined up
for .23 though, I think it should be).


Satyam

PS: All my mails to Evgeniy Dushistov never reach him. The mail.ru server
    is absolutely *evil* and simply rejects all mails unless the sender
    is already whitelisted by the reciever (!)
-
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/