linux-kernel - Re: [PATCH 1/1] VFS: introduce s

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: <20100611014253.GE31073@ZenIV.linux.org.uk>
Date:	Fri, 11 Jun 2010 02:42:53 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Artem Bityutskiy <dedekind1@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, tytso@....edu,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 1/1] VFS: introduce s_dirty accessors

On Thu, Jun 10, 2010 at 01:56:33PM +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@...ia.com>
> 
> This patch introduces 3 VFS accessors: 'sb_mark_dirty()',
> 'sb_mark_clean()', and 'sb_is_dirty()'. They simply
> set 'sb->s_dirt' or test 'sb->s_dirt'. The plan is to make
> every FS use these accessors later instead of manipulating
> the 'sb->s_dirt' flag directly.
> 
> Ultimately, this change is a preparation for the periodic
> superblock synchronization optimization which is about
> preventing the "sync_supers" kernel thread from waking up
> even if there is nothing to synchronize.
> 
> This patch does not do any functional change, just adds
> accessor functions.

Applied and pushed.  It's in for-next, which should do until Linus
comes back and picks it...
--
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/