linux-kernel - Re: [PATCH 0/7] f2fs: some fix and cleanup about flush

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: <534B374C.8030009@cn.fujitsu.com>
Date:	Mon, 14 Apr 2014 09:18:04 +0800
From:	Gu Zheng <guz.fnst@...fujitsu.com>
To:	Kim <jaegeuk.kim@...sung.com>
CC:	f2fs <linux-f2fs-devel@...ts.sourceforge.net>,
	fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/7] f2fs: some fix and cleanup about flush_merge

Hi All,
There seems to be a mistake in "[PATCH 2/7]f2fs: remove the unuseful "issue_tail" list",
and the whole patchset needs to be reworked. So please ignore this one.
Sorry for the noise.

Regards,
Gu
On 04/11/2014 05:49 PM, Gu Zheng wrote:

> Gu Zheng (7):
>   f2fs: put the bio when issue_flush completed
>   f2fs: remove the unuseful "issue_tail" list
>   f2fs: use __GFP_ZERO to avoid appending set-NULL
>   f2fs: enable flush_merge only in f2fs is not read-only
>   f2fs: add the flush_merge handle in the remount flow
>   f2fs: introduce struct flush_cmd_control to wrap the flush_merge
>     fields
>   f2fs: introduce help function {create,destroy}_flush_cmd_control
> 
>  fs/f2fs/f2fs.h    |   17 ++++++---
>  fs/f2fs/segment.c |  102 +++++++++++++++++++++++++++++++++++-----------------
>  fs/f2fs/super.c   |   32 ++++++++++++++--
>  3 files changed, 107 insertions(+), 44 deletions(-)
> 


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