Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1734505

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

Show all headers | View raw

On 9/18/17 4:31 PM, Dave Chinner wrote:
> On Mon, Sep 18, 2017 at 09:28:55AM -0600, Jens Axboe wrote:
>> On 09/18/2017 09:27 AM, Christoph Hellwig wrote:
>>> On Mon, Sep 18, 2017 at 08:26:05PM +0530, Abdul Haleem wrote:
>>>> 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);
>>>>>>  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.
> 
> Because when a user reports a data corruption, the only evidence we
> have that they are running an app that does something stupid is this
> warning in their syslogs.  Tracepoints are not useful for replacing
> warnings about data corruption vectors being triggered.

Is the full WARN_ON spew really helpful to us, though?  Certainly
the user has no idea what it means, and will come away terrified
but none the wiser.

Would a more informative printk_once() still give us the evidence
without the ZOMG I THINK I OOPSED that a WARN_ON produces?  Or do we 
want/need the backtrace?

-Eric

> It needs to be on by default, bu tI'm sure we can wrap it with
> something like an xfs_alert_tag() type of construct so the tag can
> be set in /proc/fs/xfs/panic_mask to suppress it if testers so
> desire.
> 
> Cheers,
> 
> Dave.
> 

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at         fs/iomap.c:993 Christoph Hellwig <hch@lst.de> - 2017-09-18 17:30 +0200
  Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Jens Axboe <axboe@kernel.dk> - 2017-09-18 17:30 +0200
    Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at         fs/iomap.c:993 Christoph Hellwig <hch@lst.de> - 2017-09-18 17:40 +0200
      Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Al Viro <viro@ZenIV.linux.org.uk> - 2017-09-18 17:50 +0200
        Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Jens Axboe <axboe@kernel.dk> - 2017-09-18 18:00 +0200
          Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Dave Chinner <david@fromorbit.com> - 2017-09-19 00:00 +0200
    Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Dave Chinner <david@fromorbit.com> - 2017-09-18 23:40 +0200
      Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Eric Sandeen <sandeen@sandeen.net> - 2017-09-19 00:10 +0200
        Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 "Darrick J. Wong" <darrick.wong@oracle.com> - 2017-09-19 00:10 +0200
        Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at  fs/iomap.c:993 Dave Chinner <david@fromorbit.com> - 2017-09-19 00:10 +0200

csiph-web