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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Sep 2017 17:27:06 +0200 From: Christoph Hellwig <hch@....de> To: Abdul Haleem <abdhalee@...ux.vnet.ibm.com> Cc: linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, linux-xfs <linux-xfs@...r.kernel.org>, Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...com>, linux-next <linux-next@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, chandan <chandan@...ux.vnet.ibm.com> Subject: Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at fs/iomap.c:993 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.
Powered by blists - more mailing lists