linux-kernel - Re: [PATCH 0/6] writeback fixes and trace events

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:	Thu, 5 May 2011 00:31:15 +0200
From:	Jan Kara <jack@...e.cz>
To:	Theodore Tso <tytso@....EDU>
Cc:	Dave Chinner <david@...morbit.com>,
	Wu Fengguang <fengguang.wu@...el.com>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jan Kara <jack@...e.cz>, LKML <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 0/6] writeback fixes and trace events

On Wed 04-05-11 09:12:54, Ted Tso wrote:
> On May 4, 2011, at 6:06 AM, Dave Chinner wrote:
> 
> > Does anyone actaully testing filesystems use the -mm tree? I'm
> > pretty sure that no-one in the XFS world does, and I don't think
> > that any ext4 or btrfs folk do, either....
> 
> I don't.   I agree that it really would be great if there was a separate
> git tree for the writeback changes, since that way it becomes possible to
> test just the writeback changes, and not worry about other potential
> stability problems introduced by changes in the -mm tree....
  OK. We'd still push changes to Linus via Andrew but have them also
accumulated in that tree for testing. So we'd have a branch with changes
sitting in -mm (likely to go to Linus in near future) and then possibly
other branches with things brewing for people to try out. Does that make
sense? I can setup that tree and maintain it. Or Fengguang, do you want
to do it?

								Honza

-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/