public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Alasdair G Kergon <agk@redhat.com>
Cc: linux-kernel@vger.kernel.org, mbroz@redhat.com
Subject: Re: [PATCH 01/15] dm: support ioctls on mapped devices
Date: Wed, 21 Jun 2006 20:52:06 -0700	[thread overview]
Message-ID: <20060621205206.35ecdbf8.akpm@osdl.org> (raw)
In-Reply-To: <20060621193121.GP4521@agk.surrey.redhat.com>

On Wed, 21 Jun 2006 20:31:21 +0100
Alasdair G Kergon <agk@redhat.com> wrote:

> From: Milan Broz <mbroz@redhat.com>
>  
> Extend the core device-mapper infrastructure to accept arbitrary ioctls
> on a mapped device provided that it has exactly one target and it is 
> capable of supporting ioctls.

I don't understand that.  We're taking an ioctl against a dm device and
we're passing it through to an underlying device?  Or something else?

Care to flesh this out a bit?

> [We can't use unlocked_ioctl because we need 'inode': 'file' might be NULL.
> Is it worth changing this?]

It _should_ be possible to use unlocked_ioctl() - unlocked_ioctl() would be
pretty useless if someone was passing it a NULL file*.  More details?


  reply	other threads:[~2006-06-22  3:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 19:31 [PATCH 01/15] dm: support ioctls on mapped devices Alasdair G Kergon
2006-06-22  3:52 ` Andrew Morton [this message]
2006-06-22  8:15   ` Milan Broz
2006-06-22  8:29     ` Andrew Morton
2006-06-22 15:17       ` Alasdair G Kergon
2006-06-22 16:55         ` Andrew Morton
2006-06-23  3:31           ` Kevin Corry
2006-06-23  3:49             ` Andrew Morton
2006-06-23 10:01               ` Christoph Hellwig
2006-06-23 10:00           ` Christoph Hellwig
     [not found]             ` <20060623032108.28debec2.akpm@osdl.org>
2006-06-23 13:13               ` Milan Broz
2006-06-22 13:21   ` Alasdair G Kergon
2006-07-05  3:22 ` Arnd Bergmann

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=20060621205206.35ecdbf8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=agk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@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