From: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Stephen Hemminger" <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
gregkh@suse.de
Subject: Re: [BUG] skge 0000:02:05: read data parity error
Date: Mon, 14 Jan 2008 22:41:52 +0100 [thread overview]
Message-ID: <6101e8c40801141341hcb17b08h2fd5244bccb21928@mail.gmail.com> (raw)
In-Reply-To: <20080114213453.GJ9847@does.not.exist>
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 ...
thanks, then it is only a "feature" and not bug.
>
> > Thanks,
> > Oliver
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
--
Thanks,
Oliver
next prev parent reply other threads:[~2008-01-14 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 19:57 Oliver Pinter (Pintér Olivér)
2008-01-14 20:52 ` Stephen Hemminger
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) [this message]
2008-01-14 21:48 ` Greg KH
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=6101e8c40801141341hcb17b08h2fd5244bccb21928@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--cc=bunk@kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®