linux-kernel - Re: [PATCH 01/17] BLOCK: Move functions out of buffer code [try #2]

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]

Message-ID: <20060825140825.GB10659@infradead.org>
Date:	Fri, 25 Aug 2006 15:08:25 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/17] BLOCK: Move functions out of buffer code [try #2]

On Thu, Aug 24, 2006 at 10:32:53PM +0100, David Howells wrote:
> From: David Howells <dhowells@...hat.com>
> 
> Move some functions out of the buffering code that aren't strictly buffering
> specific.  This is a precursor to being able to disable the block layer.
> 
>  (*) Moved some stuff out of fs/buffer.c:
> 
>      (*) The file sync and general sync stuff moved to fs/sync.c.
> 
>      (*) The superblock sync stuff moved to fs/super.c.
> 
>      (*) do_invalidatepage() moved to mm/truncate.c.
> 
>      (*) try_to_release_page() moved to mm/filemap.c.
> 
>  (*) Moved some related declarations between header files:
> 
>      (*) declarations for do_invalidatepage() and try_to_release_page() moved
>      	 to linux/mm.h.
> 
>      (*) __set_page_dirty_buffers() moved to linux/buffer_head.h.
> 
> Signed-Off-By: David Howells <dhowells@...hat.com>

Please remove the CONFIG_BLOCK that splipped in and should only be in the
final patch.  Otherwise ACK.
-
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/