From: Douglas Gilbert <dgilbert@interlog.com>
To: Gwendal Grignou <gwendal@google.com>
Cc: jens.axboe@oracle.com, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] Allow ATA_ passthrough command through sg.
Date: Tue, 30 Jun 2009 02:21:37 +0200 [thread overview]
Message-ID: <4A495A91.6010803@interlog.com> (raw)
In-Reply-To: <1246310665-31727-1-git-send-email-gwendal@google.com>
Strange, my utilities and packages like smartmontools
have been sending them through for at least three years.
I presume this patch allows non-root users to send these
commands. Might there be security implications if ATA
WRITE commands are sent through? Non-root users would
still need permissions on the sg device node (e.g.
/dev/sg1).
Doug Gilbert
Gwendal Grignou wrote:
> We can already send ATA specific commands using /dev/sd device files.
> This patch allow to use /dev/sg device files as well.
>
> Signed-off-by: Gwendal Grignou <gwendal@google.com>
> ---
> block/scsi_ioctl.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/block/scsi_ioctl.c b/block/scsi_ioctl.c
> index 82a0ca2..93fa53e 100644
> --- a/block/scsi_ioctl.c
> +++ b/block/scsi_ioctl.c
> @@ -186,6 +186,12 @@ void blk_set_cmd_filter_defaults(struct blk_cmd_filter *filter)
> __set_bit(GPCMD_LOAD_UNLOAD, filter->write_ok);
> __set_bit(GPCMD_SET_STREAMING, filter->write_ok);
> __set_bit(GPCMD_SET_READ_AHEAD, filter->write_ok);
> +
> + /* ATA Passthrough */
> + __set_bit(ATA_12, filter->read_ok);
> + __set_bit(ATA_12, filter->write_ok);
> + __set_bit(ATA_16, filter->read_ok);
> + __set_bit(ATA_16, filter->write_ok);
> }
> EXPORT_SYMBOL_GPL(blk_set_cmd_filter_defaults);
>
prev parent reply other threads:[~2009-06-30 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 21:24 [PATCH] Allow ATA_ passthrough command through sg Gwendal Grignou
2009-06-29 22:20 ` Alan Cox
2009-06-29 23:26 ` Jeff Garzik
2009-06-29 23:39 ` Gwendal Grignou
2009-06-30 0:21 ` Douglas Gilbert [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=4A495A91.6010803@interlog.com \
--to=dgilbert@interlog.com \
--cc=gwendal@google.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).