From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-usb@vger.kernel.org, bpf@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH 1/2] USB: core: add a way to revoke access to open USB devices
Date: Tue, 9 Aug 2022 13:30:25 +0200 [thread overview]
Message-ID: <YvJFUWOw6vyU3tc4@kroah.com> (raw)
In-Reply-To: <8512a37ce2e54f2c44a4fe10b475d61334498c4f.camel@hadess.net>
On Tue, Aug 09, 2022 at 01:15:50PM +0200, Bastien Nocera wrote:
> On Tue, 2022-08-09 at 12:32 +0200, Greg Kroah-Hartman wrote:
> > On Tue, Aug 09, 2022 at 11:42:59AM +0200, Bastien Nocera wrote:
> > > There is a need for userspace applications to open USB devices
> > > directly,
> > > for all the USB devices without a kernel-level class driver[1], and
> > > implemented in user-space.
> > >
> > > As not all devices are built equal, we want to be able to revoke
> > > access to those devices whether it's because the user isn't at the
> > > console anymore, or because the web browser, or sandbox doesn't
> > > want
> > > to allow access to that device.
> > >
> > > This commit implements the internal API used to revoke access to
> > > USB
> > > devices, given either bus and device numbers, or/and a user's
> > > effective UID.
> > >
> > > Signed-off-by: Bastien Nocera <hadess@hadess.net>
> > >
> > > [1]:
> > > Non exhaustive list of devices and device types that need raw USB
> > > access:
> > > - all manners of single-board computers and programmable chips and
> > > devices (avrdude, STLink, sunxi bootloader, flashrom, etc.)
> > > - 3D printers
> > > - scanners
> > > - LCD "displays"
> > > - user-space webcam and still cameras
> > > - game controllers
> > > - video/audio capture devices
> > > - sensors
> > > - software-defined radios
> > > - DJ/music equipment
> > > - protocol analysers
> > > - Rio 500 music player
> >
> > We can't take "footnotes" after a signed-off-by line, you know this
> > :(
>
> Where would I know this from?
To quote from our documentation:
The sign-off is a simple line at the end of the explanation for the
patch,
> checkpatch.pl doesn't warn about it.
Odd, it should. Send a patch for that? :)
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-09 11:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 9:42 [PATCH 0/2] USB: core: add a way to revoke access to open USB devices Bastien Nocera
2022-08-09 9:42 ` [PATCH 1/2] " Bastien Nocera
2022-08-09 10:32 ` Greg Kroah-Hartman
2022-08-09 11:15 ` Bastien Nocera
2022-08-09 11:30 ` Greg Kroah-Hartman [this message]
2022-08-09 11:53 ` Bastien Nocera
2022-08-09 10:35 ` Greg Kroah-Hartman
2022-08-09 11:18 ` Bastien Nocera
2022-08-09 12:52 ` Greg Kroah-Hartman
2022-08-09 13:27 ` Bastien Nocera
2022-08-09 16:31 ` Greg Kroah-Hartman
2022-08-09 17:16 ` Bastien Nocera
2022-08-09 19:43 ` Alan Stern
2022-08-09 16:46 ` Eric W. Biederman
2022-08-09 17:08 ` Bastien Nocera
2022-08-10 17:18 ` kernel test robot
2022-08-10 17:28 ` kernel test robot
2022-08-09 9:43 ` [PATCH 2/2] usb: Implement usb_revoke() BPF function Bastien Nocera
2022-08-09 10:38 ` Greg Kroah-Hartman
2022-08-09 11:18 ` Bastien Nocera
2022-08-09 12:49 ` Greg Kroah-Hartman
2022-08-09 13:27 ` Bastien Nocera
2022-08-09 14:31 ` Bastien Nocera
2022-08-09 16:33 ` Greg Kroah-Hartman
2022-08-09 17:27 ` Bastien Nocera
2022-08-18 15:08 ` Greg Kroah-Hartman
2022-08-30 14:44 ` Bastien Nocera
2022-08-30 15:10 ` Greg Kroah-Hartman
2022-08-30 16:28 ` Bastien Nocera
2022-08-09 17:22 ` Eric W. Biederman
2022-08-10 17:59 ` kernel test robot
2022-10-26 15:00 ` Bastien Nocera
2022-10-26 15:22 ` Greg Kroah-Hartman
2022-08-09 10:31 ` [PATCH 0/2] USB: core: add a way to revoke access to open USB devices Greg Kroah-Hartman
2022-08-09 11:15 ` Bastien Nocera
2022-08-09 11:29 ` Greg Kroah-Hartman
2022-08-09 17:25 ` Eric W. Biederman
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=YvJFUWOw6vyU3tc4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ebiederm@xmission.com \
--cc=hadess@hadess.net \
--cc=linux-usb@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=stern@rowland.harvard.edu \
/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