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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171030152300.GG3252168@devbig577.frc2.facebook.com>
Date:   Mon, 30 Oct 2017 08:23:00 -0700
From:   Tejun Heo <tj@...nel.org>
To:     syzbot 
        <bot+f7b556d1766502a69d85071d2ff08bd87be53d0f@...kaller.appspotmail.com>
Cc:     linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: WARNING in ata_qc_issue

Hello,

On Fri, Oct 27, 2017 at 01:19:01AM -0700, syzbot wrote:
> WARNING: CPU: 1 PID: 2909 at drivers/ata/libata-core.c:5391
> ata_qc_issue+0x519/0xea0 drivers/ata/libata-core.c:5390
...
>  sg_common_write.isra.17+0xf80/0x1c10 drivers/scsi/sg.c:806
>  sg_write+0x7a0/0xc90 drivers/scsi/sg.c:677
>  __vfs_write+0xef/0x970 fs/read_write.c:468
>  vfs_write+0x189/0x510 fs/read_write.c:518
>  SYSC_write fs/read_write.c:565 [inline]
>  SyS_write+0xef/0x220 fs/read_write.c:557

It's issuing an invalid command (data command w/o any data) via SG and
libata triggered a warning before failing the command.  The warning is
still somewhat meaningful in that if we ever hit that during normal
kernel operation, it shows the caller who's screwing up.  idk, we can
shut it up (nothing is really wrong in this case) or make it a bit
smarter (filter out invalid sg commands earlier).

Thanks.

-- 
tejun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ