From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Eric Paris <eparis@redhat.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
len.brown@intel.com
Subject: Re: BUG: scheduling while atomic in acpi_ps_complete_op
Date: Sat, 22 Aug 2009 01:24:17 +0400 [thread overview]
Message-ID: <4A8F1081.3020803@suse.de> (raw)
In-Reply-To: <1250886352.2168.83.camel@dhcp231-106.rdu.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Eric Paris пишет:
> On Sat, 2009-08-22 at 00:12 +0400, Alexey Starikovskiy wrote:
>> Hi,
>> This should be handled by abe1dfab60e1839d115930286cb421f5a5b193f3.
>
> And yet I'm getting it from linux-next today.
>
> So you are apparently failing the in_atomic_preempt_off() test but
> succeeding in your !irqs_disabled() test.
>
> Something isn't right since I'm hitting it hundreds of times on boot.
>
> -Eric
>
Ok, let's see if replacing irqs_disabled() to
in_atomic_preempt_off() helps...
Regards,
Alex.
[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 416 bytes --]
diff --git a/include/acpi/platform/aclinux.h b/include/acpi/platform/aclinux.h
index fcb8e4b..23b262b 100644
--- a/include/acpi/platform/aclinux.h
+++ b/include/acpi/platform/aclinux.h
@@ -152,7 +152,7 @@ static inline void *acpi_os_acquire_object(acpi_cache_t * cache)
#define ACPI_PREEMPTION_POINT() \
do { \
- if (!irqs_disabled()) \
+ if (!in_atomic_preempt_off()) \
cond_resched(); \
} while (0)
next prev parent reply other threads:[~2009-08-21 21:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 16:55 BUG: scheduling while atomic in acpi_ps_complete_op Eric Paris
2009-08-21 20:12 ` Alexey Starikovskiy
2009-08-21 20:25 ` Eric Paris
2009-08-21 21:24 ` Alexey Starikovskiy [this message]
2009-08-24 14:36 ` Eric Paris
2009-08-24 14:50 ` Vegard Nossum
2009-08-25 21:20 ` Eric Paris
2009-08-26 1:00 ` ykzhao
2009-08-26 11:58 ` Eric Paris
2009-08-26 14:13 ` ykzhao
2009-08-26 18:48 ` Eric Paris
2009-08-27 5:39 ` Ming Lei
2009-08-26 12:20 ` Eric Paris
2009-08-26 2:12 ` Paul E. McKenney
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=4A8F1081.3020803@suse.de \
--to=astarikovskiy@suse.de \
--cc=eparis@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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