linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, hch@infradead.org,
	dm <dm-devel@redhat.com>,
	linux-next@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [dm-devel] linux-next: Tree for Feb 2 (drivers/md/dm.c)
Date: Thu, 2 Feb 2017 10:44:10 -0800	[thread overview]
Message-ID: <20170202184409.GA27869@infradead.org> (raw)
In-Reply-To: <20170202182916.GA26910@redhat.com>

On Thu, Feb 02, 2017 at 01:29:16PM -0500, Mike Snitzer wrote:
> Are you trying to say that this happens using a certain .config?
> 
> Also, not sure why you didn't cc Christoph (or Jens) seeing as these
> changes are _not_ staged in linux-next by linux-dm.git.

No changes to dm caused this, it was me making the SCSI ioctl / request
code optional.  The tree apparently has nothing pulling in the SCSI
ioctls (SCSI, IDE, virtio, cciss, target, cdrom, etc).  It turns
out DM calls the SCSI ioctl verification functions, despite never
actually using SCSIO ioctls directly, which looks very odd (and which is
why I missed it).

Git-blame for these lines pointes to ... me.  Heh.  But I just moved the
code around, before that every target had a copy of it.  The original
calls seem to come from:

ec8013bedd ("dm: do not forward ioctls from logical volumes to the
underlying device"),

The trivial fix would be to add a select of the SCSI_REQUEST symbol
to dm, but my gut feeling teels me the call is simply wrong, and
should be removed and instead all ioctls on DM devices that don't
map to a full underlying devices should be rejected.

  reply	other threads:[~2017-02-02 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02  7:21 linux-next: Tree for Feb 2 Stephen Rothwell
2017-02-02 17:58 ` linux-next: Tree for Feb 2 (drivers/md/dm.c) Randy Dunlap
2017-02-02 18:29   ` Mike Snitzer
2017-02-02 18:44     ` Christoph Hellwig [this message]
2017-02-02 20:19       ` [dm-devel] " Paolo Bonzini

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=20170202184409.GA27869@infradead.org \
    --to=hch@infradead.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).