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  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, 6 Mar 2019 13:11:39 +0100 (CET)
From:   Jiri Kosina <>
To:     Vlastimil Babka <>,
        Andrew Morton <>
cc:     Linus Torvalds <>,,,, Peter Zijlstra <>,
        Greg KH <>,
        Jann Horn <>,
        Andy Lutomirski <>,
        Cyril Hrubis <>, Daniel Gruss <>,
        Dave Chinner <>,
        Dominique Martinet <>,
        Kevin Easton <>,
        "Kirill A. Shutemov" <>,
        Matthew Wilcox <>, Tejun Heo <>
Subject: Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments

On Wed, 30 Jan 2019, Vlastimil Babka wrote:

> I've collected the patches from the discussion for formal posting. The first
> two should be settled already, third one is the possible improvement I've
> mentioned earlier, where only in restricted case we resort to existence of page
> table mapping (the original and later reverted approach from Linus) instead of
> faking the result completely. Review and testing welcome.
> The consensus seems to be going through -mm tree for 5.1, unless Linus wants
> them alredy for 5.0.
> Jiri Kosina (2):
>   mm/mincore: make mincore() more conservative
>   mm/filemap: initiate readahead even if IOCB_NOWAIT is set for the I/O
> Vlastimil Babka (1):
>   mm/mincore: provide mapped status when cached status is not allowed


could you please take at least the correct and straightforward fix for 
mincore() before we figure out how to deal with the slightly less 
practical RWF_NOWAIT? Thanks.

Jiri Kosina

Powered by blists - more mailing lists