From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [IPV4 3/5] fib_trie: dump doesnt use RCU
Date: Thu, 24 Jan 2008 07:41:08 +0100 [thread overview]
Message-ID: <47983304.3030309@trash.net> (raw)
In-Reply-To: <20080123.205007.16809712.davem@davemloft.net>
David Miller wrote:
> From: Stephen Hemminger <shemminger@linux-foundation.org>
> Date: Wed, 23 Jan 2008 14:48:47 -0800
>
>
>> Since fib dump (via netlink) holds the RTNL mutex, it is unnecessary
>> to use RCU, and it is impossible to get truncated (-EBUSY) result.
>>
>> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>>
>
> You tested this patch, right? :-/
>
> The whole reason we need the nlk->cb[] state is to hold things across
> multiple recvmsg() calls that might be necessary to obtain the full
> dump.
>
> rtnetlink goes:
>
> rtnl_lock();
> netlink_rcv_skb(skb, &rtnetlink_rcv_msg);
> ...
> static int rtnetlink_rcv_msg(struct sk_buff *skb, struct nlmsghdr *nlh)
> {
> ...
> if (kind == 2 && nlh->nlmsg_flags&NLM_F_DUMP) {
> struct sock *rtnl;
> rtnl_dumpit_func dumpit;
>
> dumpit = rtnl_get_dumpit(family, type);
> if (dumpit == NULL)
> return -EOPNOTSUPP;
>
> __rtnl_unlock();
> rtnl = net->rtnl;
> err = netlink_dump_start(rtnl, skb, nlh, dumpit, NULL);
> rtnl_lock();
> return err;
>
> (NOTE: Drops RTNL semaphore for netlink_dump_start() call)
>
> ...
> int netlink_dump_start(struct sock *ssk, struct sk_buff *skb,
> struct nlmsghdr *nlh,
> int (*dump)(struct sk_buff *skb,
> struct netlink_callback *),
> int (*done)(struct netlink_callback *))
> {
> ...
> cb->dump = dump;
> cb->done = done;
> cb->nlh = nlh;
> atomic_inc(&skb->users);
> cb->skb = skb;
> ...
> mutex_lock(nlk->cb_mutex);
> ...
> nlk->cb = cb;
> mutex_unlock(nlk->cb_mutex);
>
> netlink_dump(sk);
> ...
>
> static int netlink_dump(struct sock *sk)
> {
> ...
> mutex_lock(nlk->cb_mutex);
> ...
> len = cb->dump(skb, cb);
>
> if (len > 0) {
> mutex_unlock(nlk->cb_mutex);
> skb_queue_tail(&sk->sk_receive_queue, skb);
> sk->sk_data_ready(sk, len);
> return 0;
> }
>
> (NOTE: Therefore cb->dump() runs without RTNL semaphore held)
>
> ...
> static int netlink_recvmsg(struct kiocb *kiocb, struct socket *sock,
> struct msghdr *msg, size_t len,
> int flags)
> {
> ...
> if (nlk->cb && atomic_read(&sk->sk_rmem_alloc) <= sk->sk_rcvbuf / 2)
> netlink_dump(sk);
> ...
>
> Therefore, that RTNL assertion you added should have triggered on any
> dump you may have tried since ->dump() is always invoked without the
> RTNL semaphore since rtnetlink drops it around the ->dump() call and
> the call chain for this fib_trie cause would be:
>
> inet_dump_fib()
> fn_trie_dump()
>
> and nothing in that code path retakes the RTNL semaphore.
Actually we're always holding the rtnl during dumps, nlk->cb_mutex points
to rtnl_mutex in case of rtnetlink. It used to be held only during the first
->dump invocation and not on continuations, but I changed this a few
versions
ago.
next prev parent reply other threads:[~2008-01-24 6:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080123224844.610730277@linux-foundation.org>
2008-01-23 22:48 ` [IPV4 1/5] fib_trie: more whitespace cleanup Stephen Hemminger
2008-01-24 4:37 ` David Miller
2008-01-23 22:48 ` [IPV4 2/5] fib_trie: remove unneeded NULL check Stephen Hemminger
2008-01-24 4:38 ` David Miller
2008-01-23 22:48 ` [IPV4 3/5] fib_trie: dump doesnt use RCU Stephen Hemminger
2008-01-24 4:50 ` David Miller
2008-01-24 6:41 ` Patrick McHardy [this message]
2008-01-24 6:43 ` David Miller
2008-01-24 6:47 ` Patrick McHardy
2008-01-24 7:26 ` David Miller
2008-01-24 6:45 ` Stephen Hemminger
2008-01-24 7:27 ` David Miller
2008-01-24 21:51 ` [PATCH] fib_trie: rescan if key is lost during dump Stephen Hemminger
2008-01-25 8:23 ` Jarek Poplawski
2008-01-25 16:13 ` Stephen Hemminger
2008-01-25 19:01 ` Jarek Poplawski
2008-02-01 0:45 ` David Miller
2008-01-23 22:48 ` [IPV4 4/5] fib_trie: version 0.410 Stephen Hemminger
2008-01-24 4:50 ` David Miller
2008-01-23 22:48 ` [IPV4 5/5] fib_semantics: sparse warnings Stephen Hemminger
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=47983304.3030309@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).