From: Jens Axboe <axboe@suse.de>
To: Elias da Silva <silva@aurigatec.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/block/scsi_ioctl.c, Video DVD playback support
Date: Tue, 25 Jan 2005 17:21:02 +0100 [thread overview]
Message-ID: <20050125162102.GS2751@suse.de> (raw)
In-Reply-To: <200501251713.27402.silva@aurigatec.de>
On Tue, Jan 25 2005, Elias da Silva wrote:
> On Tuesday 25 January 2005 13:45, you wrote:
> [snip]
> : If I'm not mistaken, Peter Jones has posted a few iterations of such an
> : fs some months ago.
>
> Thank you. I will check this...
>
> : > Do we have a clear understanding that this fs would only
> : > be a benefit if *All* the different ways to access the device would
> : > use the same policy enforcement and consistently allow or
> : > disallow certain operations regardless of the access method?
> :
> : The command restriction table _only_ works through the SG_IO path, which
> : does include CDROM_SEND_PACKET as well since it is layered on top of
> : SG_IO. It doesn't control various driver ioctl exported interfaces, they
> : would need to add a callback to verify_command() for permission checks.
>
> Hmm... what exactly does that mean? Who is ment by "_they_ would need..."?
It refers back to 'various driver ioctl' earlier, so it refers to the
driver itself.
--
Jens Axboe
next prev parent reply other threads:[~2005-01-25 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 2:27 [PATCH] drivers/block/scsi_ioctl.c, Video DVD playback support Elias da Silva
2005-01-24 8:36 ` Jens Axboe
2005-01-24 19:59 ` Elias da Silva
2005-01-24 20:39 ` Jens Axboe
2005-01-24 22:10 ` Elias da Silva
2005-01-25 0:01 ` Alan Cox
2005-01-25 8:05 ` Jens Axboe
2005-01-25 9:29 ` Elias da Silva
2005-01-25 12:44 ` Alan Cox
2005-01-25 15:52 ` Elias da Silva
2005-01-25 12:45 ` Jens Axboe
2005-01-25 16:13 ` Elias da Silva
2005-01-25 16:21 ` Jens Axboe [this message]
2005-01-25 16:28 ` Elias da Silva
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=20050125162102.GS2751@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=silva@aurigatec.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.