From: Peter Zijlstra <peterz@infradead.org>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jeff Garzik <jgarzik@pobox.com>,
IngIngo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: mmotm 2011-06-22 - inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
Date: Thu, 23 Jun 2011 17:38:36 +0200 [thread overview]
Message-ID: <1308843516.1022.139.camel@twins> (raw)
In-Reply-To: <6189.1308794391@turing-police.cc.vt.edu>
On Wed, 2011-06-22 at 21:59 -0400, Valdis.Kletnieks@vt.edu wrote:
> [ 20.254275] {SOFTIRQ-ON-W} state was registered at:
> [ 20.254275] [<ffffffff8106973b>] mark_irqflags+0xf2/0x13e
> [ 20.254275] [<ffffffff810699b2>] __lock_acquire+0x22b/0x3e2
> [ 20.254275] [<ffffffff8106a09f>] lock_acquire+0x103/0x153
> [ 20.254275] [<ffffffff8157bb01>] _raw_spin_lock+0x36/0x45
> [ 20.254275] [<ffffffff8110ddf8>] end_writeback+0x33/0x103
> [ 20.254275] [<ffffffff81125425>] bdev_evict_inode+0x3e/0xbe
> [ 20.254275] [<ffffffff8110df78>] evict+0xb0/0x173
> [ 20.254275] [<ffffffff8110e1ea>] iput_final+0x171/0x17a
> [ 20.254275] [<ffffffff8110e241>] iput+0x4e/0x53
> [ 20.254275] [<ffffffff81125cad>] __blkdev_put+0x1c0/0x1eb
> [ 20.254275] [<ffffffff81125ebe>] blkdev_put+0x1e6/0x1f5
> [ 20.254275] [<ffffffff8121d143>] register_disk+0xea/0x13c
> [ 20.254275] [<ffffffff8121d2c4>] add_disk+0x12f/0x1a4
> [ 20.254275] [<ffffffff812ef339>] sd_probe_async+0x115/0x1b5
> [ 20.254275] [<ffffffff8105ce2f>] async_run_entry_fn+0x99/0x12a
> [ 20.254275] [<ffffffff810505e8>] process_one_work+0x25d/0x467
> [ 20.254275] [<ffffffff81051ddb>] worker_thread+0x152/0x206
> [ 20.254275] [<ffffffff810561fa>] kthread+0x7f/0x87
> [ 20.254275] [<ffffffff815835d4>] kernel_thread_helper+0x4/0x10
That looks broken. Not having -mm, is there a git tree some place?, I
cannot quite see how end_writeback() is taking mapping->tree_lock as my
version looks like:
void end_writeback(struct inode *inode)
{
might_sleep();
BUG_ON(inode->i_data.nrpages);
BUG_ON(!list_empty(&inode->i_data.private_list));
BUG_ON(!(inode->i_state & I_FREEING));
BUG_ON(inode->i_state & I_CLEAR);
inode_sync_wait(inode);
/* don't need i_lock here, no concurrent mods to i_state */
inode->i_state = I_FREEING | I_CLEAR;
}
and I couldn't find tree_lock used in inode_sync_wait() either.
Anyway, mapping->tree_lock is supposed to be an IRQ-safe lock, look at
all the spin_lock_irq(&mapping->tree_lock) usage in mm/filemap.c.
next prev parent reply other threads:[~2011-06-23 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 20:05 mmotm 2011-06-22-13-05 uploaded akpm
2011-06-23 0:45 ` Stephen Rothwell
2011-06-23 1:59 ` mmotm 2011-06-22 - inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage Valdis.Kletnieks
2011-06-23 15:38 ` Peter Zijlstra [this message]
2011-06-23 16:02 ` Valdis.Kletnieks
2011-06-23 16:08 ` Peter Zijlstra
2011-06-23 19:59 ` Jan Kara
2011-06-27 2:49 ` mmotm 2011-06-22-13-05 uploaded KAMEZAWA Hiroyuki
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=1308843516.1022.139.camel@twins \
--to=peterz@infradead.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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