From: Greg KH <gregkh@suse.de>
To: "Oliver Pinter (Pint?r Oliv?r)" <oliver.pntr@gmail.com>
Cc: Adrian Bunk <bunk@kernel.org>,
Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [BUG] skge 0000:02:05: read data parity error
Date: Mon, 14 Jan 2008 13:48:28 -0800 [thread overview]
Message-ID: <20080114214828.GA8128@suse.de> (raw)
In-Reply-To: <6101e8c40801141341hcb17b08h2fd5244bccb21928@mail.gmail.com>
On Mon, Jan 14, 2008 at 10:41:52PM +0100, Oliver Pinter (Pint?r Oliv?r) wrote:
> On 1/14/08, Adrian Bunk <bunk@kernel.org> wrote:
> > On Mon, Jan 14, 2008 at 10:31:03PM +0100, Oliver Pinter (Pint?r Oliv?r)
> > wrote:
> > > I think, it is a potential security breakpoint, when applications with
> > > root permission its read, then a machine is freezed, or only i thin
> > > it's?
> >
> > When you are root there are infinite ways to kill your machine, so
> > there's nothing security related about this issue.
>
> Yes, i know, but when some application or daemons read some file with
> running root privileges, then ...
It's always been that way, this is nothing new.
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-14 21:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 19:57 [BUG] skge 0000:02:05: read data parity error Oliver Pinter (Pintér Olivér)
2008-01-14 20:52 ` Stephen Hemminger
2008-01-14 20:52 ` Stephen Hemminger
2008-01-14 21:01 ` Adrian Bunk
2008-01-14 21:01 ` Adrian Bunk
2008-01-14 21:30 ` Greg KH
2008-01-14 21:31 ` Oliver Pinter (Pintér Olivér)
2008-01-14 21:34 ` Adrian Bunk
2008-01-14 21:41 ` Oliver Pinter (Pintér Olivér)
2008-01-14 21:48 ` Greg KH [this message]
2008-01-14 21:52 ` Adrian Bunk
2008-01-14 21:58 ` Oliver Pinter (Pintér Olivér)
2008-01-14 22:37 ` Stephen Hemminger
2008-01-14 21:38 ` Greg KH
2008-01-14 21:44 ` Oliver Pinter (Pintér Olivér)
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=20080114214828.GA8128@suse.de \
--to=gregkh@suse.de \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=shemminger@linux-foundation.org \
/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.