Re: [PATCH 01/15] dm: support ioctls on mapped devices

[Andrew Morton]

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

> From: Milan Broz <mbroz@xxxxxxxxxx>
>  
> 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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/