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] [day] [month] [year] [list]
Date:   Sat, 29 Aug 2020 08:02:30 +0100
From:   Christoph Hellwig <>
To:     Arnd Bergmann <>
Cc:     Minchan Kim <>,
        Andrew Morton <>,
        LKML <>,
        Christian Brauner <>,
        linux-mm <>,
        Linux API <>,
        Oleksandr Natalenko <>,
        Suren Baghdasaryan <>,
        Tim Murray <>,
        Sandeep Patil <>,
        Sonny Rao <>,
        Brian Geffon <>,
        Michal Hocko <>,
        Johannes Weiner <>,
        Shakeel Butt <>,
        John Dias <>,
        Joel Fernandes <>,
        Jann Horn <>,,
        SeongJae Park <>,
        David Rientjes <>,
        Arjun Roy <>,
        Vlastimil Babka <>,
        Christian Brauner <>,
        Daniel Colascione <>,
        Jens Axboe <>,
        Kirill Tkhai <>,
        SeongJae Park <>,
        linux-man <>
Subject: Re: [PATCH v8 3/4] mm/madvise: introduce process_madvise() syscall:
 an external memory hinting API

On Fri, Aug 28, 2020 at 07:40:08PM +0200, Arnd Bergmann wrote:
> Every syscall that passes an iovec seems to do this. If we make import_iovec()
> handle both cases directly, this syscall and a number of others can
> be simplified, and you avoid the x32 entry point I mentioned above

FYI, I do have a series that does this (even tested) and kills tons of
compat syscalls by that.  But by doing that I found the problem that
compat syscalls issued by io_uring don't trigger in_compat_syscall().
I need to go back to fixing the io_uring vs in_compat_syscall() issue
(probably for 5.9) and then submit the whole thing.

Powered by blists - more mailing lists