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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Sep 2017 16:43:29 +0100
From:   Al Viro <>
To:     Christoph Hellwig <>
Cc:     Jens Axboe <>,
        Abdul Haleem <>,
        linuxppc-dev <>,
        linux-xfs <>,
        linux-next <>,
        linux-kernel <>,
        chandan <>
Subject: Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at

On Mon, Sep 18, 2017 at 05:39:47PM +0200, Christoph Hellwig wrote:
> On Mon, Sep 18, 2017 at 09:28:55AM -0600, Jens Axboe wrote:
> > If it's expected, why don't we kill the WARN_ON_ONCE()? I get it all
> > the time running xfstests as well.
> Dave insisted on it to decourage users/applications from mixing
> mmap and direct I/O.
> In many ways a tracepoint might be the better way to diagnose these.

sysctl suppressing those two, perhaps?

Powered by blists - more mailing lists