From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ULI 2.6.12
Date: Mon, 04 Apr 2005 13:45:35 +0000 [thread overview]
Message-ID: <20050404134535.GA9920@infradead.org> (raw)
In-Reply-To: <20050401130602.A123752@goliath.americas.sgi.com>
On Mon, Apr 04, 2005 at 08:31:44AM -0500, Michael Raymond wrote:
> Again the idea is that the handler function was registered by root or
> some priviledged developer making a conscious decision. This is currently
> protected by permissions on the /dev/uli file. If you'd like me to add
> permission checks to the kernel functions I'd be happy to do it.
No, that's not the point. User level interrupts are totally pointless if
they can cause the same problems on misbehaviour.
prev parent reply other threads:[~2005-04-04 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 19:06 [PATCH] ULI 2.6.12 Michael Raymond
2005-04-04 0:22 ` Peter Chubb
2005-04-04 7:09 ` Christoph Hellwig
2005-04-04 13:31 ` Michael Raymond
2005-04-04 13:45 ` Christoph Hellwig [this message]
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=20050404134535.GA9920@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@vger.kernel.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