From: "Jonathan Lemon" <jonathan.lemon@gmail.com>
To: Netdev <netdev@vger.kernel.org>
Subject: rtnl_lock() question
Date: Tue, 03 Sep 2019 14:55:17 -0700 [thread overview]
Message-ID: <29EC5179-D939-42CD-8577-682BE4B05916@gmail.com> (raw)
How appropriate is it to hold the rtnl_lock() across a sleepable
memory allocation? On one hand it's just a mutex, but it would
seem like it could block quite a few things.
--
Jonathan
next reply other threads:[~2019-09-03 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 21:55 Jonathan Lemon [this message]
2019-09-04 7:39 ` rtnl_lock() question Eric Dumazet
2019-09-04 16:38 ` Jonathan Lemon
2019-09-04 23:23 ` Saeed Mahameed
2019-09-05 18:07 ` Rustad, Mark D
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=29EC5179-D939-42CD-8577-682BE4B05916@gmail.com \
--to=jonathan.lemon@gmail.com \
--cc=netdev@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