[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ef71e74-848f-59d4-6b0b-d3a3c52095a0@c-s.fr>
Date: Fri, 29 Nov 2019 17:14:18 +0100
From: Christophe Leroy <christophe.leroy@....fr>
To: Jens Axboe <axboe@...nel.dk>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
Pavel Begunkov <asml.silence@...il.com>
Cc: stable@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Build failure on latest powerpc/merge (311ae9e159d8 io_uring: fix
dead-hung for non-iter fixed rw)
Le 29/11/2019 à 17:04, Jens Axboe a écrit :
> On 11/29/19 6:53 AM, Christophe Leroy wrote:
>> CC fs/io_uring.o
>> fs/io_uring.c: In function ‘loop_rw_iter’:
>> fs/io_uring.c:1628:21: error: implicit declaration of function ‘kmap’
>> [-Werror=implicit-function-declaration]
>> iovec.iov_base = kmap(iter->bvec->bv_page)
>> ^
>> fs/io_uring.c:1628:19: warning: assignment makes pointer from integer
>> without a cast [-Wint-conversion]
>> iovec.iov_base = kmap(iter->bvec->bv_page)
>> ^
>> fs/io_uring.c:1643:4: error: implicit declaration of function ‘kunmap’
>> [-Werror=implicit-function-declaration]
>> kunmap(iter->bvec->bv_page);
>> ^
>>
>>
>> Reverting commit 311ae9e159d8 ("io_uring: fix dead-hung for non-iter
>> fixed rw") clears the failure.
>>
>> Most likely an #include is missing.
>
> Huh weird how the build bots didn't catch that. Does the below work?
Yes it works, thanks.
Christophe
Powered by blists - more mailing lists