All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Adel Gadllah <adel.gadllah@gmail.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	pjones@redhat.com, dgilbert@interlog.com, matthew@wil.cx,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] cmdfilter: extend default read filter
Date: Thu, 26 Jun 2008 19:43:31 +0200	[thread overview]
Message-ID: <20080626174331.GF20851@kernel.dk> (raw)
In-Reply-To: <6cf6b73e0806260853v2c8fb475u2a53bcdf20b8ae70@mail.gmail.com>

On Thu, Jun 26 2008, Adel Gadllah wrote:
> 2008/6/26 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>:
> > On Fri, 27 Jun 2008 00:08:46 +0900
> > FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> >
> >> On Thu, 26 Jun 2008 17:05:50 +0200
> >> "Adel Gadllah" <adel.gadllah@gmail.com> wrote:
> >>
> >> > 2008/6/26 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>:
> >> > > On Thu, 26 Jun 2008 12:10:25 +0200
> >> > > "Adel Gadllah" <adel.gadllah@gmail.com> wrote:
> >> > >
> >> > >> 2008/6/18 Peter Jones <pjones@redhat.com>:
> >> > >> > Douglas Gilbert wrote:
> >> > >> >>
> >> > >> >> Peter Jones wrote:
> >> > >> >>>
> >> > >> >>> FUJITA Tomonori wrote:
> >> > >> >>>
> >> > >> >>>> Well, this changes sg behaviour since sg's allow_ops filter has a
> >> > >> >>>> access permission different from blk_verify_command filter's.
> >> > >> >>>
> >> > >> >>>  >
> >> > >> >>>>
> >> > >> >>>> I guess that the first thing you need to do is that figuring out a
> >> > >> >>>> proper access permission for each command, which sg maintainer, etc
> >> > >> >>>> can agree. It's pretty hard and that's the reason why this patch has
> >> > >> >>>> not been merged for years, I think.
> >> > >> >>>
> >> > >> >>> I don't think this logic is sound.
> >> > >> >>
> >> > >> >> That depends on your viewpoint.
> >> > >> >
> >> > >> > My viewpoint is this:
> >> > >> >
> >> > >> > 1) Whether you agree with his reasons or not, Linus made it pretty clear
> >> > >> > that he's against removing the command filter (see
> >> > >> > http://marc.info/?l=linux-scsi&m=115419945212450&w=2 )
> >> > >> > 2) Having different code paths use different filtering code just adds more
> >> > >> > confusion.
> >> > >> > 3) If we're going to have filtering, it should be configurable on a
> >> > >> > per-device basis from userland.
> >> > >> >
> >> > >> > Which of these do you disagree with?
> >> > >> >
> >> > >> > [...]
> >> > >> >>
> >> > >> >> Are per device command filters being proposed?
> >> > >> >
> >> > >> > Yes, that's what the patch implements.  And it allows the userland to
> >> > >> > configure them according to the needs of the hardware.
> >> > >>
> >> > >> Jens can we add merge this for .27 or does anyone still has objections?
> >> > >
> >> > > I think that this patch makes sg's permission stricter. So this could
> >> > > break the existing user-space applications.
> >> > >
> >> >
> >> > any particular app in mind?
> >>
> >> No, but there would be some.
> >>
> >>
> >> > for write access it still allows all commands (because there are some
> >> > userspace apps tha rely on this).
> >>
> >> Yeah, I know. But for read access, some commands will be blocked.
> >
> > I think that it's not a good idea to say "this patch could break
> > something but we have no idea about them. So we can merge this."
> >
> > It's better to loosen scsi_ioctl's permissions to match with sg's
> > permission.
> 
> agreed.
> 
> Jens please apply the attached patch on top of the old one.

Thanks, I thought this had already been worked out when I saw the
previous discussion. Please verify that this patch then no longer causes
ANY different behaviour than what we already have, that's a prerequisite
for merging it.

I've applied this patch.

-- 
Jens Axboe


  reply	other threads:[~2008-06-26 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 15:53 [PATCH] cmdfilter: extend default read filter Adel Gadllah
2008-06-26 17:43 ` Jens Axboe [this message]
2008-06-26 18:04   ` Adel Gadllah
2008-06-26 18:06     ` Jens Axboe

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=20080626174331.GF20851@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=adel.gadllah@gmail.com \
    --cc=dgilbert@interlog.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=pjones@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 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.