From: Ying Xue <ying.xue@windriver.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>, <alexei@purestorage.com>,
<joern@purestorage.com>, <ja@ssi.bg>, <davem@davemloft.net>
Subject: Re: [PATCH net-next 0/6] neigh cleanups and fixes
Date: Mon, 18 May 2015 11:30:24 +0800 [thread overview]
Message-ID: <55595CD0.9060403@windriver.com> (raw)
In-Reply-To: <1431692082.27831.92.camel@edumazet-glaptop2.roam.corp.google.com>
On 05/15/2015 08:14 PM, Eric Dumazet wrote:
> atomic_read() by definition are unsafe.
Can you please recommend which atomic interface can be safely used to check
whether neigh refcnt is zero in the first patch?
Thanks,
Ying
prev parent reply other threads:[~2015-05-18 3:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 6:55 [PATCH net-next 0/6] neigh cleanups and fixes Ying Xue
2015-05-15 6:55 ` [PATCH net-next 1/6] net: fix a double free issue for neighbour entry Ying Xue
2015-05-15 6:55 ` [PATCH net-next 2/6] neigh: fix a possible leak issue of neigh entry Ying Xue
2015-05-15 12:12 ` Eric Dumazet
2015-05-15 15:39 ` David Miller
2015-05-18 3:24 ` Ying Xue
2015-05-18 4:58 ` Eric Dumazet
2015-05-18 5:55 ` Ying Xue
2015-05-18 12:54 ` Eric Dumazet
2015-05-15 6:55 ` [PATCH net-next 3/6] neigh: don't delete neighbour time in neigh_destroy Ying Xue
2015-05-15 6:55 ` [PATCH net-next 4/6] neigh: align the usage of neigh timer with one of sock timer Ying Xue
2015-05-15 6:55 ` [PATCH net-next 5/6] neigh: neigh dead and timer variables should be protected under its lock Ying Xue
2015-05-15 6:55 ` [PATCH net-next 6/6] neigh: use standard interface to modify timer Ying Xue
2015-05-15 12:14 ` [PATCH net-next 0/6] neigh cleanups and fixes Eric Dumazet
2015-05-15 15:40 ` David Miller
2015-05-18 3:30 ` Ying Xue [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=55595CD0.9060403@windriver.com \
--to=ying.xue@windriver.com \
--cc=alexei@purestorage.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=ja@ssi.bg \
--cc=joern@purestorage.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;
as well as URLs for NNTP newsgroup(s).