From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec-next] xfrm: Use VRF master index if output device is enslaved
Date: Wed, 19 Aug 2015 22:36:59 +0200 [thread overview]
Message-ID: <20150819203659.GA11165@secunet.com> (raw)
In-Reply-To: <55D4CC8B.1080306@cumulusnetworks.com>
On Wed, Aug 19, 2015 at 11:35:55AM -0700, David Ahern wrote:
> >
> >I think you should use the new vrf_master_index() helper that acquires rcu because
> >it looks possible to call ->decode_session() without rcu read lock, e.g. in the hold_timer
> >function xfrm_policy_queue_process(), though I haven’t tested it and might be missing
> >something. :-)
>
> I was digging into code paths yesterday. Today I added WARN_ON and
> seems like the rcu_read_lock is held:
>
> if (skb_dst(skb)) {
> WARN_ON(!rcu_read_lock_held() && !rcu_read_lock_bh_held());
> oif = vrf_master_ifindex_rcu(skb_dst(skb)->dev) ?
> : skb_dst(skb)->dev->ifindex;
> pr_info("_decode_session: oif %d skb_dst(skb)->dev->ifindex %d\n",
> oif, skb_dst(skb)->dev->ifindex);
> }
>
> I get the printk, but not the WARN_ON splat.
Well, this depends on the codepath that called xfrm_decode_session().
It really think it was not called through xfrm_policy_queue_process()
because this codepath is just used if the sysctl xfrm_larval_drop is switched
off (on by default) and the required xfrm_state is not yet established.
prev parent reply other threads:[~2015-08-19 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 15:54 [PATCH ipsec-next] xfrm: Use VRF master index if output device is enslaved David Ahern
2015-08-19 12:47 ` Nikolay Aleksandrov
2015-08-19 18:35 ` David Ahern
2015-08-19 20:36 ` Steffen Klassert [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=20150819203659.GA11165@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
/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.