linux-kernel - Re: linux-next: manual merge of the vfs tree with the tree

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]

Date:	Mon, 25 May 2009 00:07:47 +0200
From:	Christoph Hellwig <hch@....de>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Al Viro <viro@...IV.linux.org.uk>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: linux-next: manual merge of the vfs tree with the  tree

On Mon, May 25, 2009 at 12:03:38AM +0200, Frederic Weisbecker wrote:
> > + 	if (s->s_dirt)
> > + 		reiserfs_write_super(s);
> 
> 
> 
> But this part seems to solve another conflict, right?
> I'm not sure about it.

Yes, different one.  Previously the VFS called ->write_super just before
->put_super.  Now any left over writeback needs to be dealt with by
the filesystem.  For now I have added a call to the write_super method
to all filesystems, but most likely this can be removed later after
an audit by someone who knows the filesystem.

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