linux-kernel - Re: fs: move bdev code out of buffer.c

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090401111003.GZ28946@ZenIV.linux.org.uk>
Date:	Wed, 1 Apr 2009 12:10:03 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: fs: move bdev code out of buffer.c

On Mon, Mar 30, 2009 at 11:55:24AM -0700, Andrew Morton wrote:

> This patch moved the CONFIG_BLOCK=y declaration of freeze_bdev() out of
> buffer_head.h and into fs.h.  But it left the CONFIG_BLOCK=n definition
> of freeze_bdev() in buffer_head.h.

Actually, there's more.
	a) fsync_bdev() export is left behind in buffer.c
	b) sync_blockdev/invalidate_bdev are like freeze_bdev/thaw_bdev -
non-block stubs need to be moved.

Fixed and pushed into for-next
--
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/