Thread (11 messages) 11 messages, 7 authors, 2017-09-18

Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at fs/iomap.c:993

From: Jens Axboe <axboe@kernel.dk>
Date: 2017-09-18 15:29:02
Also in: linux-next, linux-xfs, lkml

On 09/18/2017 09:27 AM, Christoph Hellwig wrote:
On Mon, Sep 18, 2017 at 08:26:05PM +0530, Abdul Haleem wrote:
quoted
Hi,

A warning is triggered from:

file fs/iomap.c in function iomap_dio_rw

    if (ret)
        goto out_free_dio;

    ret = invalidate_inode_pages2_range(mapping,
            start >> PAGE_SHIFT, end >> PAGE_SHIFT);
quoted
quoted
 WARN_ON_ONCE(ret);
    ret = 0;

    inode_dio_begin(inode);
This is expected and an indication of a problematic workload - which
may be triggered by a fuzzer.
If it's expected, why don't we kill the WARN_ON_ONCE()? I get it all
the time running xfstests as well.

-- 
Jens Axboe
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help