From: Arjan van de Ven <arjan@infradead.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew Morton <akpm@osdl.org>,
olaf+list.linux-kernel@olafdietsche.de, eike-kernel@sf-tec.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.16-rc1-git4] accessfs: a permission managing filesystem
Date: Mon, 30 Jan 2006 11:39:10 +0100 [thread overview]
Message-ID: <1138617550.2977.24.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0601301135540.12495@yvahk01.tjqt.qr>
On Mon, 2006-01-30 at 11:36 +0100, Jan Engelhardt wrote:
> >
> >well... maybe.
> >If you need to mess inside irq context, spinlocks sound more the right
> >thing. Or if you need to do a "I'm done" in the irq and a "sleep until
> >done" thing in process context, then you really should use completions
> >instead.
>
> Hm, is it allowed to call copy_{from,to}_user() in irq context?
absolutely not.
IRQ context has no defined "userspace" context at all, so even if
copy_from/to_user wouldn't sleep (they do, and that alone makes it
"illegal" to do already) it would be highly undefined what you would be
copying to/from.
next prev parent reply other threads:[~2006-01-30 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 21:06 [PATCH] 2.6.15: access permission filesystem 0.17 Olaf Dietsche
2006-01-14 22:45 ` Ingo Oeser
2006-01-15 21:22 ` Olaf Dietsche
2006-01-23 11:57 ` Rolf Eike Beer
2006-01-28 22:27 ` [PATCH 2.6.16-rc1-git4] accessfs: a permission managing filesystem Olaf Dietsche
2006-01-28 23:01 ` Andrew Morton
2006-01-29 22:47 ` Olaf Dietsche
2006-01-30 9:07 ` Jan Engelhardt
2006-01-30 9:16 ` Andrew Morton
2006-01-30 9:24 ` Jan Engelhardt
2006-01-30 9:32 ` Andrew Morton
2006-01-30 9:46 ` Arjan van de Ven
2006-01-30 9:51 ` Jan Engelhardt
2006-01-30 9:54 ` Arjan van de Ven
2006-01-30 10:25 ` Jan Engelhardt
2006-01-30 10:31 ` Arjan van de Ven
2006-01-30 10:36 ` Jan Engelhardt
2006-01-30 10:39 ` Arjan van de Ven [this message]
2006-01-30 10:46 ` Jan Engelhardt
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=1138617550.2977.24.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=eike-kernel@sf-tec.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf+list.linux-kernel@olafdietsche.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
all inboxes | Powered by JetHome®