linux-kernel - Re: [PATCH 0/16] Make O_SYNC handling use standard syncing path (version 4)

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, 2 Sep 2009 16:16:45 +0200
From:	Christoph Hellwig <hch@....de>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	hch@....de
Subject: Re: [PATCH 0/16] Make O_SYNC handling use standard syncing path (version 4)

On Wed, Sep 02, 2009 at 03:59:10PM +0200, Jan Kara wrote:
>   Hi,
> 
>   here is a new version of my O_SYNC cleanup patches. There are two minor
> changes since last time. XFS now uses filemap_write_and_wait() as Christoph
> asked

The XFS tree now does this already, Idid it as part of the XFS-internal
fsync/O_SYNC consolidation.  I'll look into fixing the data writeout
stuff ontop of you series, and after that XFS can use the generic
helper, too.

>   If noone objects, I think the patch series is ready to be put in linux-next.

I'll look through it, but in general the sooner we have this in -next,
the better.

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