linux-kernel - Re: linux-next: Tree for Jun 18 (fs/io

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] [day] [month] [year] [list]

Message-ID: <52b64a82-34c2-268f-7aa3-4cb4f7a14e23@kernel.dk>
Date:   Thu, 18 Jun 2020 08:42:00 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Al Viro <viro@...IV.linux.org.uk>
Subject: Re: linux-next: Tree for Jun 18 (fs/io_uring)

On 6/17/20 11:38 PM, Randy Dunlap wrote:
> On 6/17/20 9:15 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: there will be no linux-next release tomorrow.
>>
>> Changes since 20200617:
>>
> 
> when CONFIG_BLOCK is not set/enabled:
> 
> ../fs/io_uring.c: In function 'io_async_task_func':
> ../fs/io_uring.c:4559:7: error: implicit declaration of function 'io_sq_thread_acquire_mm'; did you mean 'atomic_read_acquire'? [-Werror=implicit-function-declaration]
>    if (io_sq_thread_acquire_mm(ctx, req)) {
>        ^~~~~~~~~~~~~~~~~~~~~~~
>        atomic_read_acquire
> ../fs/io_uring.c: In function 'io_sq_thread':
> ../fs/io_uring.c:6268:4: error: implicit declaration of function 'io_sq_thread_drop_mm'; did you mean 'io_sq_thread'? [-Werror=implicit-function-declaration]
>     io_sq_thread_drop_mm(ctx);
>     ^~~~~~~~~~~~~~~~~~~~
>     io_sq_thread

Fixed it up, thanks.

-- 
Jens Axboe