On Fri, 2007-09-07 at 18:01 +0200, Michael Buesch wrote: > What's the problem with trying to lock it? I think I had a problem with it once when I inserted it into some code that was atomic and it all blew up badly ;) Nothing important really but it sort of made me not like it much. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- From: Herbert Xu <herbert@gondor.apana.org.au>
- Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
- Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- From: Johannes Berg <johannes@sipsolutions.net>
- Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- From: Michael Buesch <mb@bu3sch.de>
- Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- Prev by Date: Re: [PATCH 1/2][RESEND] improve generic_file_buffered_write()
- Next by Date: Re: [patch 1/6] Linux Kernel Markers - Architecture Independent Code
- Previous by thread: Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- Next by thread: Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170
- Index(es):
![]() |