linux-kernel - Re: [PATCH take 2 01/28] VFS: introduce writeback_inodes

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:	Wed, 7 May 2008 08:38:35 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Artem Bityutskiy <dedekind@...dex.ru>
Cc:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Adrian Hunter <ext-adrian.hunter@...ia.com>,
	Edward Shishkin <edward.shishkin@...il.com>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH take 2 01/28] VFS: introduce writeback_inodes_sb()

On Wed, 07 May 2008 14:14:41 +0300 Artem Bityutskiy <dedekind@...dex.ru> wrote:

> Hi Andrew,
> 
> Andrew Morton wrote:
> > This looks rather similar to
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-sb_sync_inodes.patch
> > 
> > Which is best?
> 
> Well, this reiser4 patch is basically doing 3 things at once:
> 1. Introduce ->sync_inodes()
> 2. Move spin_lock(&inode_lock);
> 3. Export generic_sync_sb_inodes()
> 
> As Christoph suggested, I've attached a patch which just moves the
> spinlock. Could you please consider sending it to Linus or taking into your tree?

I already added gti-ubifs.patch to the -mm lineup.  I haven't yet tried
pulling, merging or compiling it.

I'd suggest that you just retain this patch in your tree.

> Should I amend the reiser4 patch correspondingly for you?

That would be nice, if you have time, thanks.

> Also, what do you think about taking UBIFS into your tree?

I take git trees pretty promiscuously, to get them a bit more exposure and
merge/build testing.

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