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  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:   Tue, 22 Jun 2021 19:23:24 +0100
From:   David Howells <>
To:     Linus Torvalds <>
Cc:, Matthew Wilcox <>,
        Al Viro <>, "Ted Ts'o" <>,
        Dave Hansen <>,
        Andrew Morton <>,
        Linux-MM <>,
        Ext4 Developers List <>,
        linux-fsdevel <>,
        Linux Kernel Mailing List <>
Subject: Re: Do we need to unrevert "fs: do not prefault sys_write() user buffer pages"?

Linus Torvalds <> wrote:

> I'm not sure how that would even look. I don't think it would
> necessarily be *impossible* (special marker in the exception table to
> let the fault code know that this is a "prepare" fault), but it would
> be pretty challenging.

Probably the most obvious way would be to set a flag in task_struct saying
what you're doing and have the point that would otherwise wait for the page to
become unlocked skip to the fault fixup code if the page is locked after
->readahead() has been invoked and the flag is set, then use get_user() in

But, as Willy says, there's a reasonable chance that the source page is
present anyway (presumably you want to write out data you've just constructed
or modified), in which case it's probably not worth the complexity.


Powered by blists - more mailing lists