public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, jurriaan <thunder7@xs4all.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc4: lots of 'in_atomic():1, irqs_disabled():0' with  software-raid1
Date: Fri, 29 Aug 2008 17:36:08 +1000	[thread overview]
Message-ID: <18615.42728.498883.440973@notabene.brown> (raw)
In-Reply-To: message from Andrew Morton on Thursday August 28

On Thursday August 28, akpm@linux-foundation.org wrote:
> 
> I'm curious about how this happened.
> 
> afaict from reading the code, this:
> 
> 	rcu_read_lock();
> 	might_sleep();
> 	rcu_read_unlock();
> 
> will warn if CONFIG_PREEMPT_RCU=n but won't warn if
> CONFIG_PREEMPT_RCU=y.  If correct, that's a nasty trap.
> 
> Is that what you did?

Uhm..
$ grep PREEMPT /home/src/md-x86-64/.config
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
$ grep DEBUG_SPIN /home/src/md-x86-64/.config
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
$ grep RCU /home/src/md-x86-64/.config
CONFIG_CLASSIC_RCU=y
# CONFIG_RCU_TORTURE_TEST is not set

This definitely doesn't report an error if I put "might_sleep" inside 
rcu_read_lock.  I tried to figure out why but got lost.

BTW, I need the following to get current -git to compile.

NeilBrown

Author: NeilBrown <neilb@suse.de>
Date:   Tue Aug 19 11:59:37 2008 +1000

    Fix compile error in security

diff --git a/include/linux/security.h b/include/linux/security.h
index 2ee5ecf..0cc23a1 100644
--- a/include/linux/security.h
+++ b/include/linux/security.h
@@ -1757,7 +1757,7 @@ static inline int security_ptrace_may_access(struct task_struct *child,
 
 static inline int security_ptrace_traceme(struct task_struct *child)
 {
-	return cap_ptrace_traceme(parent);
+	return cap_ptrace_traceme(child);
 }
 
 static inline int security_capget(struct task_struct *target,



  reply	other threads:[~2008-08-29  7:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 17:05 2.6.27-rc4: lots of 'in_atomic():1, irqs_disabled():0' with software-raid1 jurriaan
2008-08-27 21:47 ` Rafael J. Wysocki
2008-08-28  7:33   ` Jens Axboe
2008-08-28  7:45     ` Andrew Morton
2008-08-28  7:48       ` Jens Axboe
2008-08-28  7:56         ` Andre Noll
2008-08-28  8:11           ` Jens Axboe
2008-08-28  8:04             ` Andre Noll
2008-08-28  8:27         ` Neil Brown
2008-08-28  8:36           ` Jens Axboe
2008-08-28  9:00           ` Andrew Morton
2008-08-29  7:36             ` Neil Brown [this message]
2008-08-29  7:47               ` Jens Axboe
2008-08-29  8:14               ` Andrew Morton
2008-08-29  5:44           ` Neil Brown
2008-08-29  5:48             ` Neil Brown
2008-08-29  7:11               ` Jens Axboe

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=18615.42728.498883.440973@notabene.brown \
    --to=neilb@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=thunder7@xs4all.nl \
    /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