From: Paolo Bonzini <pbonzini@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
linux-scsi@vger.kernel.org, jbottomley@parallels.com,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: Can we pass a file handle down to the block ioctls to implement per file filters on scsi SG_IO ?
Date: Tue, 12 Jun 2012 21:13:54 +0200 [thread overview]
Message-ID: <4FD794F2.2080000@redhat.com> (raw)
In-Reply-To: <20120612195200.2a1b6129@pyramind.ukuu.org.uk>
Il 12/06/2012 20:52, Alan Cox ha scritto:
> > Sure; however, doing so requires access to some member of "struct file"
> > from SG_IO. Thus, ioctl would need to take a "struct file" rather than
> > just an fmode_t.
> >
> > The switch to fmode_t was done in 2007 by Al Viro. I would like to
> > understand the reasons for the switch; it seems to me that it was part
> > of the big kernel lock removal. If it's acceptable to undo it, I would
> > very much would like to add generic BPF filtering to SG_IO
>
> That would solve all sorts of problems in this area, so lets ping the man
> himself - Al ?
(Even if he says no, we could probably use cgroups instead).
Paolo
next prev parent reply other threads:[~2012-06-12 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 16:08 [PATCH] scsi: allow persistent reservations without CAP_SYS_RAWIO Paolo Bonzini
2012-06-12 16:21 ` James Bottomley
2012-06-12 16:24 ` Paolo Bonzini
2012-06-12 16:54 ` Paolo Bonzini
2012-06-12 16:54 ` Paolo Bonzini
2012-06-12 17:20 ` James Bottomley
2012-06-12 17:25 ` Paolo Bonzini
2012-06-12 18:02 ` James Bottomley
2012-06-12 18:39 ` Paolo Bonzini
2012-06-12 16:55 ` Alan Cox
2012-06-12 17:08 ` Paolo Bonzini
2012-06-12 18:52 ` Can we pass a file handle down to the block ioctls to implement per file filters on scsi SG_IO ? Alan Cox
2012-06-12 19:13 ` Paolo Bonzini [this message]
2012-06-12 17:08 ` [PATCH] scsi: allow persistent reservations without CAP_SYS_RAWIO John Stoffel
2012-06-12 17:13 ` Paolo Bonzini
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=4FD794F2.2080000@redhat.com \
--to=pbonzini@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@kernel.dk \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.