linux-ext4 - Re: [PATCH] ext4: fix ext4_flush_completed

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: <20121003202438.GA6026@thunk.org>
Date:	Wed, 3 Oct 2012 16:24:38 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	linux-ext4@...r.kernel.org, jack@...e.cz
Subject: Re: [PATCH] ext4: fix ext4_flush_completed_IO wait semantics

On Wed, Oct 03, 2012 at 11:32:27PM +0400, Dmitry Monakhov wrote:
> On Wed, 3 Oct 2012 14:55:58 -0400, "Theodore Ts'o" <tytso@....edu> wrote:
> > Are you planning on updating the 'ext4: completed_io locking cleanup
> > V4' patch series, or is this an additional patch that should be tacked
> > on to it?
> This is addidional patch which should be placed on top of
> 'ext4: completed_io locking cleanup V4'
> I'll try to convince Jan Kara that this is the best way to fix both bugs.

OK, thanks.  I've been making the spelling/typo fixes suggested by Jan
to the commits in my tree.  So we're up to date on that front.  I just
wanted to know if there were any other changes you think were
necessary to the patch series.

I'll add the completed_io locking cleanup to my patch series, and
start running tests....

						- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html