From: Greg KH <greg@kroah.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
"E. Oltmanns" <oltmanns@uni-bonn.de>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops during usb usage (2.6.5)
Date: Mon, 26 Apr 2004 15:31:05 -0700 [thread overview]
Message-ID: <20040426223101.GA9258@kroah.com> (raw)
In-Reply-To: <200404270017.34478.oliver@neukum.org>
On Tue, Apr 27, 2004 at 12:17:34AM +0200, Oliver Neukum wrote:
> Am Montag, 26. April 2004 21:53 schrieb Greg KH:
> > On Mon, Apr 26, 2004 at 01:06:15PM -0400, Bill Davidsen wrote:
> > > Just in general, if there is anything a non-root user can do to crash
> > > the system, it's probably a kernel bug by definition. It doesn't matter
> > > that's it a stupid thing to do, it might be malicious. And in this case
> > > it might just be user error.
> >
> > But you either have to be root in order to talk to usbfs, or you were
> > root when you gave a user access to the usbfs node. So either way, a
> > "normal" user can't even do this.
>
> Greg,
>
> that's not an answer. It in effect means that usbfs is useless.
Heh. So the correct answer is:
- don't do that. Talking to the same device through usbfs at
the same time by multiple programs is cause for lots of bad
things to happen to your device, and might possibly cause it
to hang. If you want to allow a user to access a device
through usbfs, make sure you trust them.
Better? :)
thanks,
greg k-h
next prev parent reply other threads:[~2004-04-26 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 20:56 Kernel Oops during usb usage (2.6.5) E. Oltmanns
2004-04-24 0:30 ` Greg KH
2004-04-26 17:06 ` Bill Davidsen
2004-04-26 19:53 ` Greg KH
2004-04-26 22:17 ` Oliver Neukum
2004-04-26 22:31 ` Greg KH [this message]
2004-04-27 9:04 ` Oliver Neukum
2004-04-27 11:06 ` Duncan Sands
2004-04-26 22:53 ` E. Oltmanns
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=20040426223101.GA9258@kroah.com \
--to=greg@kroah.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=oltmanns@uni-bonn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox