From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@163.com>
Cc: netfilter-devel@vger.kernel.org, Liping Zhang <zlpnobody@gmail.com>
Subject: Re: [PATCH nf] netfilter: make it safer during the inet6_dev->addr_list traversal
Date: Sat, 8 Apr 2017 23:33:27 +0200 [thread overview]
Message-ID: <20170408213327.GC5301@salvia> (raw)
In-Reply-To: <1491125273-8002-1-git-send-email-zlpnobody@163.com>
On Sun, Apr 02, 2017 at 05:27:53PM +0800, Liping Zhang wrote:
> From: Liping Zhang <zlpnobody@gmail.com>
>
> inet6_dev->addr_list is protected by inet6_dev->lock, so only using
> rcu_read_lock is not enough, we should acquire read_lock_bh(&idev->lock)
> before the inet6_dev->addr_list traversal.
Applied, thanks.
prev parent reply other threads:[~2017-04-08 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 9:27 [PATCH nf] netfilter: make it safer during the inet6_dev->addr_list traversal Liping Zhang
2017-04-08 21:33 ` Pablo Neira Ayuso [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=20170408213327.GC5301@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.com \
--cc=zlpnobody@gmail.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.