linux-kernel - Re: [linux-next][bock] [bisected c20cfc27a] WARNING: CPU: 22 PID: 0 at block/blk-core.c:2655 .blk_update

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 10 May 2017 09:56:42 +0200
From:   Christoph Hellwig <hch@....de>
To:     Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
Cc:     Jens Axboe <axboe@...nel.dk>, hch@....de,
        sachinp <sachinp@...ux.vnet.ibm.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-block <linux-block@...r.kernel.org>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [linux-next][bock] [bisected c20cfc27a] WARNING: CPU: 22 PID:
        0 at block/blk-core.c:2655 .blk_update_request+0x4f8/0x500

On Tue, May 09, 2017 at 08:48:21PM +0530, Abdul Haleem wrote:
> A bisection for the above suspects resulted a bad commit;
> 
> c20cfc27a47307e811346f85959cf3cc07ae42f9 is the first bad commit
> commit c20cfc27a47307e811346f85959cf3cc07ae42f9
> Author: Christoph Hellwig <hch@....de>
> Date:   Wed Apr 5 19:21:07 2017 +0200
> 
>     block: stop using blkdev_issue_write_same for zeroing

And this effectively switches us to use the write_zeroes for SCSI.



>     
>     We'll always use the WRITE ZEROES code for zeroing now.
>     
>     Signed-off-by: Christoph Hellwig <hch@....de>
>     Reviewed-by: Martin K. Petersen <martin.petersen@...cle.com>
>     Reviewed-by: Hannes Reinecke <hare@...e.com>
>     Signed-off-by: Jens Axboe <axboe@...com>
> 
> 
> @Christoph FYI, the machine configured with 64K page size
> > 
> > WARNING: CPU: 12 PID: 0 at block/blk-core.c:2651 .blk_update_request+0x4cc/0x4e0

Can you decode which warning this is?  Is it:

	WARN_ON_ONCE(req->rq_flags & RQF_SPECIAL_PAYLOAD);

?  In which case your setup did a partial completion of a WRITE SAME
command, which is perfectly legal according to SCSI, but a bit unusual.