From: Taehee Yoo <ap420073@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next] mld: add missing rtnl_lock() in do_ipv6_getsockopt()
Date: Wed, 31 Mar 2021 01:13:25 +0900 [thread overview]
Message-ID: <fd15f71e-1e91-210c-e067-9c0a43250bd8@gmail.com> (raw)
In-Reply-To: <CANn89iKeeWLkzrrW8Yre+iHkbfL6kLR33vDae8y01Hfn-nz5_A@mail.gmail.com>
On 3/31/21 1:08 AM, Eric Dumazet wrote:
> On Tue, Mar 30, 2021 at 6:02 PM Taehee Yoo <ap420073@gmail.com> wrote:
>>
>> On 3/31/21 12:40 AM, Eric Dumazet wrote:
>> > This seems a serious regression compared to old code (in net tree)
>> >
>> > Have you added RTNL requirement in all this code ?
>> >
>> > We would like to use RTNL only if strictly needed.
>>
>> Yes, I agree with you.
>> This patchset actually relies on existed RTNL, which is
>> setsockopt_needs_rtnl().
>> And remained RTNL was replaced by mc_lock.
>> So, this patchset actually doesn't add new RTNL except in this case.
>>
>> Fortunately, I think It can be replaced by RCU because,
>> 1. ip6_mc_msfget() doesn't need the sleepable functions.
>> 2. It is not the write critical section.
>> So, RCU can be used instead of RTNL for ip6_mc_msfget().
>> How do you think about it?
>
> Yes please, do not add RTNL here if we can avoid it.
>
Okay, I will send a new patch.
> Otherwise some applications will slow down the whole stack, even with
> different containers/netns.
>
> (There is a single RTNL for the whole machine)
>
Thanks a lot for the review!
prev parent reply other threads:[~2021-03-30 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 15:31 [PATCH net-next] mld: add missing rtnl_lock() in do_ipv6_getsockopt() Taehee Yoo
2021-03-30 15:40 ` Eric Dumazet
2021-03-30 16:02 ` Taehee Yoo
2021-03-30 16:08 ` Eric Dumazet
2021-03-30 16:13 ` Taehee Yoo [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=fd15f71e-1e91-210c-e067-9c0a43250bd8@gmail.com \
--to=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).