From: Jens Axboe <jens.axboe@oracle.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: lockdep warning during elevator_switch
Date: Tue, 2 Feb 2010 21:58:30 +0100 [thread overview]
Message-ID: <20100202205830.GJ5733@kernel.dk> (raw)
In-Reply-To: <alpine.LSU.2.00.1001312327260.7190@sister.anvils>
On Sun, Jan 31 2010, Hugh Dickins wrote:
> From 2.6.33-rc3 onwards, PROVE_LOCKING=y gives me the warning below when
> I "echo deadline >/sys/block/sdb/queue/scheduler" to change it from cfq.
>
> Backing out 846f99749ab68bbc7f75c74fec305de675b1a1bf "sysfs: Add lockdep
> annotations for the sysfs active reference" stops the warning -
> but I realize that doesn't mean the actual problem (if any) is fixed.
Thanks Hugh, I hadn't noticed this yet. I do online switches all the
time, but depending on tests lockdep may not be enabled (it steals all
my performance...). I'll take a look.
--
Jens Axboe
prev parent reply other threads:[~2010-02-02 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 23:55 lockdep warning during elevator_switch Hugh Dickins
2010-02-02 20:58 ` Jens Axboe [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=20100202205830.GJ5733@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=ebiederm@xmission.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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