From: Greg KH <greg@kroah.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "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 12:53:59 -0700 [thread overview]
Message-ID: <20040426195359.GA29062@kroah.com> (raw)
In-Reply-To: <408D4187.2040104@tmr.com>
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.
thanks,
greg k-h
next prev parent reply other threads:[~2004-04-26 20:20 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 [this message]
2004-04-26 22:17 ` Oliver Neukum
2004-04-26 22:31 ` Greg KH
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=20040426195359.GA29062@kroah.com \
--to=greg@kroah.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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