From: Al Viro <viro@ZenIV•linux.org.uk>
To: Stephen Hemminger <shemminger@vyatta•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Rusty Russell <rusty@rustcorp•com.au>,
Peter Oberparleiter <oberpar@linux•vnet.ibm.com>,
Miklos Szeredi <mszeredi@suse•cz>,
Eric Dumazet <eric.dumazet@gmail•com>,
"Paul E. McKenney" <paulmck@linux•vnet.ibm.com>,
"David S. Miller" <davem@davemloft•net>,
Jiri Pirko <jpirko@redhat•com>, Jiri Olsa <jolsa@redhat•com>,
Ingo Molnar <mingo@elte•hu>,
Alexey Dobriyan <adobriyan@gmail•com>,
Jamal Hadi Salim <hadi@cyberus•ca>,
Neil Horman <nhorman@tuxdriver•com>,
netdev@vger•kernel.org
Subject: Re: [PATCH 1/3] seq_file: add RCU versions of new hlist/list iterators (v3)
Date: Fri, 19 Feb 2010 22:22:39 +0000 [thread overview]
Message-ID: <20100219222239.GN30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20100219220111.692855800@vyatta.com>
On Fri, Feb 19, 2010 at 01:59:14PM -0800, Stephen Hemminger wrote:
> Many usages of seq_file use RCU protected lists, so non RCU
> iterators will not work safely.
Looks sane, provided that you give strong warnings about access to
contents of list elements...
next prev parent reply other threads:[~2010-02-19 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 21:59 [PATCH 0/3] Convert packet and key sockets to RCU Stephen Hemminger
2010-02-19 21:59 ` [PATCH 1/3] seq_file: add RCU versions of new hlist/list iterators (v3) Stephen Hemminger
2010-02-19 22:22 ` Al Viro [this message]
2010-02-19 21:59 ` [PATCH 2/3] packet: convert socket list to RCU (v2) Stephen Hemminger
2010-02-19 22:23 ` [PATCH] packet: convert socket list to RCU (v3) Stephen Hemminger
2010-02-20 3:39 ` Eric Dumazet
2010-02-19 21:59 ` [PATCH 3/3] af_key: locking change Stephen Hemminger
2010-02-20 4:07 ` Eric Dumazet
2010-02-20 5:53 ` Stephen Hemminger
2010-02-20 20:51 ` David Miller
[not found] <20100222175716.900955428@vyatta.com>
2010-02-22 17:57 ` [PATCH 1/3] seq_file: add RCU versions of new hlist/list iterators (v3) Stephen Hemminger
2010-02-22 23:46 ` David Miller
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=20100219222239.GN30031@ZenIV.linux.org.uk \
--to=viro@zeniv$(echo .)linux.org.uk \
--cc=adobriyan@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=hadi@cyberus$(echo .)ca \
--cc=jolsa@redhat$(echo .)com \
--cc=jpirko@redhat$(echo .)com \
--cc=mingo@elte$(echo .)hu \
--cc=mszeredi@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@tuxdriver$(echo .)com \
--cc=oberpar@linux$(echo .)vnet.ibm.com \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
--cc=rusty@rustcorp$(echo .)com.au \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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