public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "zdi-disclosures@trendmicro.com" <zdi-disclosures@trendmicro.com>,
	"security@kernel.org" <security@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
	linux-scsi@vger.kernel.org
Subject: Re: ZDI-CAN-17016: New Vulnerability Report
Date: Tue, 5 Apr 2022 07:53:42 +0200	[thread overview]
Message-ID: <20220405055342.GB23698@lst.de> (raw)
In-Reply-To: <20220404091211.GA12805@kadam>

On Mon, Apr 04, 2022 at 12:12:11PM +0300, Dan Carpenter wrote:
> This is a valid double copy bug.  I think/hope that /dev/dpt_i2o can
> only be opened by root so I'm going to CC the public lists.
> 
> Last week we deleted the PMCRAID_PASSTHROUGH_IOCTL ioctl in commit
> f16aa285e618 ("scsi: pmcraid: Remove the PMCRAID_PASSTHROUGH_IOCTL ioctl
> implementation").  The temptation is to delete I2OUSRCMD as well.

I'm all for it.  In fact given how bad the driver is I would not be
sad to see it gone, but last time this came up about 5 years ago there
still were users.

      reply	other threads:[~2022-04-05  5:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM5PR0102MB34776506CDCC1E2FFCF78C4580E09@DM5PR0102MB3477.prod.exchangelabs.com>
2022-04-04  9:12 ` ZDI-CAN-17016: New Vulnerability Report Dan Carpenter
2022-04-05  5:53   ` Christoph Hellwig [this message]

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=20220405055342.GB23698@lst.de \
    --to=hch@lst.de \
    --cc=aacraid@microsemi.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=security@kernel.org \
    --cc=zdi-disclosures@trendmicro.com \
    /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