From: Kirill Korotaev <dev@sw.ru>
To: linux-kernel@vger.kernel.org
Subject: [BUG?] dev_close() is called with locks held
Date: Fri, 19 Nov 2004 12:02:50 +0300 [thread overview]
Message-ID: <419DB6BA.5040901@sw.ru> (raw)
Hello,
looks like a bug in 2.4/2.6 kernels:
1. dev_close() function is blocking. it calls schedule() inside and
calls blocking dev_deactivate() function.
2. But... call chain
dev_ioctl() -> dev_ifsioc() -> dev_change_flags() calls dev_close()
under read_lock(&dev_base_lock)...
Bug?
Kirill
next reply other threads:[~2004-11-19 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 9:02 Kirill Korotaev [this message]
2004-11-19 9:40 ` [BUG?] dev_close() is called with locks held Patrick McHardy
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=419DB6BA.5040901@sw.ru \
--to=dev@sw.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.