linux-ext4 - Re: [PATCH 1/2] ext4: Allow unlocked direct IO when pages are cached

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: <20160930055629.uu2gt3ykigb24yho@thunk.org>
Date:   Fri, 30 Sep 2016 01:56:29 -0400
From:   Theodore Ts'o <tytso@....edu>
To:     Jan Kara <jack@...e.cz>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: [PATCH 1/2] ext4: Allow unlocked direct IO when pages are cached

On Tue, Sep 27, 2016 at 04:22:27PM +0200, Jan Kara wrote:
> Currently we do not allow unlocked (meaning without inode_lock) direct
> IO when the file has any pages cached. This check is not needed anymore
> as we keep inode lock until ext4_direct_IO_write() and thus can happily
> writeback and evict any pages conflicting with current direct IO write.
> 
> Signed-off-by: Jan Kara <jack@...e.cz>

Thanks, applied.

						- 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