From: Nigel Cunningham <ncunningham@cyclades.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Patrick Mochel <mochel@digitalimplant.org>,
Christoph Lameter <christoph@lameter.com>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH] Workqueue freezer support.
Date: Mon, 08 Aug 2005 11:38:07 +1000 [thread overview]
Message-ID: <1123465087.3969.152.camel@localhost> (raw)
In-Reply-To: <200508081127.48432.kernel@kolivas.org>
Hi.
On Mon, 2005-08-08 at 11:27, Con Kolivas wrote:
> On Mon, 8 Aug 2005 10:46 am, Nigel Cunningham wrote:
> > Hi.
> >
> > Sorry for the slow response. Busy still.
> >
> > On Sat, 2005-08-06 at 15:06, Patrick Mochel wrote:
> > > On Fri, 5 Aug 2005, Nigel Cunningham wrote:
> > > > Hi.
> > > >
> > > > I finally found some time to finish this off. I don't really like the
> > > > end result - the macros looked clearer to me - but here goes. If it
> > > > looks okay, I'll seek sign offs from each of the affected driver
> > > > maintainers and from Ingo. Anyone else?
> > >
> > > What are your feelings about this: http://lwn.net/Articles/145417/ ?
> >
> > I'm sure it could work, but I do worry a little about the possibilities
> > for exploits. It seems to me that if someone can get root, they an
> > insmod a module that could schedule any kind of work via any process.
> > Tracing that sort of security hole could be intractable. Christoph, is
> > that something you've considered/have thoughts on? Perhaps I'm just
> > being paranoid :>
>
> If someone gets root access it means you're already exploited.
Yeah, true. Ok. Lame thought :>
Nigel
> Cheers,
> Con
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
next prev parent reply other threads:[~2005-08-08 1:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 5:17 [PATCH] Workqueue freezer support Nigel Cunningham
2005-07-21 15:38 ` [linux-pm] " Pavel Machek
2005-07-21 15:42 ` Ingo Molnar
2005-07-21 15:44 ` Pavel Machek
2005-07-21 19:42 ` Patrick Mochel
2005-07-22 3:02 ` Nigel Cunningham
2005-08-05 12:12 ` Nigel Cunningham
2005-08-06 5:06 ` Patrick Mochel
2005-08-08 0:46 ` Nigel Cunningham
2005-08-08 1:27 ` Con Kolivas
2005-08-08 1:38 ` Nigel Cunningham [this message]
2005-08-08 12:18 ` Nigel Cunningham
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=1123465087.3969.152.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=christoph@lameter.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mochel@digitalimplant.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