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:   Sun, 19 Feb 2017 09:25:41 -0800
From:   Christoph Hellwig <>
To:     Al Viro <>
Cc:     James Bottomley <>,
        Dmitry Vyukov <>,
        Johannes Thumshirn <>,
        "Martin K. Petersen" <>,
        linux-scsi <>,
        LKML <>,
        syzkaller <>,
        Hannes Reinecke <>,
        Linus Torvalds <>
Subject: Re: scsi: BUG in scsi_init_io

On Sun, Feb 19, 2017 at 07:15:27AM +0000, Al Viro wrote:
> The root cause is unfixable without access to TARDIS and dose of
> antipsychotics sufficient to prevent /dev/sg API creation.
> What happens is that write to /dev/sg is given a request with non-zero
> ->iovec_count combined with zero ->dxfer_len.  Or with ->dxferp pointing
> to an array full of empty iovecs.
> AFAICS, the minimal fix would be something like this:
> YAMissingSanityCheck in /dev/sg
> write permission to /dev/sg shouldn't be equivalent to the ability to trigger
> BUG_ON() while holding spinlocks...

Looks fine to me:

Reviewed-by: Christoph Hellwig <>

The other thing we really need to consider is to finally merge the
SG_IO implementations for /dev/sg with the common block layer one.

Powered by blists - more mailing lists