From: "kernel list" <list.kernel@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: list.kernel@gmail.com
Subject: vmlist_lock locking
Date: Fri, 8 Dec 2006 02:07:50 -0500 [thread overview]
Message-ID: <a574553e0612072307v766c3742pd3b4c46fb4fd0470@mail.gmail.com> (raw)
My understanding is that get_vm_area_node etc. can't be called in
interrupt context because vmlist_lock is obtained with read_lock /
write_lock. I am wondering if it makes sense to use read_lock_bh /
write_lock_bh so that get_vm_area_node can be called in soft interrupt
context. All the code executed when holding vmlist_lock is walking
through the list, so it shouldn't change the behavior. If it does make
sense, BUG_ON(in_interrupt()) can be changed to BUG_ON(in_irq()).
next reply other threads:[~2006-12-08 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 7:07 kernel list [this message]
2006-12-08 7:40 ` Eric Dumazet
2006-12-12 9:58 ` Jarek Poplawski
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=a574553e0612072307v766c3742pd3b4c46fb4fd0470@mail.gmail.com \
--to=list.kernel@gmail.com \
--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
all inboxes | Powered by JetHome®