From: Luis Henriques <luis.henriques@canonical.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH v3 part1 0/4] Fix SG_IO ambiguity between READ SUBCHANNEL and UNMAP (and other similar cases)
Date: Wed, 27 Aug 2014 10:34:37 +0100 [thread overview]
Message-ID: <20140827093437.GA10937@hercules> (raw)
In-Reply-To: <1369317503-4095-1-git-send-email-pbonzini@redhat.com>
On Thu, May 23, 2013 at 03:58:19PM +0200, Paolo Bonzini wrote:
> The SG_IO ioctl's command whitelist is designed for MMC devices (roughly,
> "play/burn CDs without requiring root") but some opcodes overlap across SCSI
> device classes and have different meanings for different classes.
>
> To fix this, use different bitmaps for the various device classes.
> This is CVE-2012-4542.
>
Sorry for bringing this old issue again, but I was wondering what
happen to this fix.
Cheers,
--
Luís
> v2->v3: patches are now split differently, according to Tejun's indications;
> added conflict on operation code A4h.
>
> Paolo Bonzini (4):
> sg_io: pass request_queue to blk_verify_command
> sg_io: prepare to introduce per-class command filters
> sg_io: use different default filters for each device class
> sg_io: resolve conflicts between commands assigned to multiple classes
> (CVE-2012-4542)
>
> block/bsg.c | 2 +-
> block/scsi_ioctl.c | 193 +++++++++++++++++++++++++++--------------------
> drivers/scsi/scsi_scan.c | 2 +
> drivers/scsi/sg.c | 3 +-
> include/linux/blkdev.h | 5 +-
> 5 files changed, 118 insertions(+), 87 deletions(-)
>
> --
> 1.8.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2014-08-27 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 13:58 [PATCH v3 part1 0/4] Fix SG_IO ambiguity between READ SUBCHANNEL and UNMAP (and other similar cases) Paolo Bonzini
2013-05-23 13:58 ` [PATCH v3 part1 1/4] sg_io: pass request_queue to blk_verify_command Paolo Bonzini
2013-05-24 7:36 ` James Bottomley
2013-05-24 7:43 ` Paolo Bonzini
2013-05-24 7:50 ` James Bottomley
2013-05-24 7:53 ` Paolo Bonzini
2013-05-24 8:03 ` James Bottomley
2013-05-24 8:32 ` Paolo Bonzini
2013-05-24 21:41 ` Paolo Bonzini
2013-05-25 4:14 ` James Bottomley
2013-05-25 6:18 ` Paolo Bonzini
2013-05-23 13:58 ` [PATCH v3 part1 2/4] sg_io: prepare to introduce per-class command filters Paolo Bonzini
2013-05-23 13:58 ` [PATCH v3 part1 3/4] sg_io: use different default filters for each device class Paolo Bonzini
2013-05-23 13:58 ` [PATCH v3 part1 4/4] sg_io: resolve conflicts between commands assigned to multiple classes (CVE-2012-4542) Paolo Bonzini
2014-08-27 9:34 ` Luis Henriques [this message]
2014-08-27 10:09 ` [PATCH v3 part1 0/4] Fix SG_IO ambiguity between READ SUBCHANNEL and UNMAP (and other similar cases) Paolo Bonzini
2014-08-27 12:08 ` Luis Henriques
2014-08-27 17:47 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140827093437.GA10937@hercules \
--to=luis.henriques@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox