public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@diku.dk>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: paulmck@linux.vnet.ibm.com,
	Jesper Dangaard Brouer <hawk-4UpuNZONu4c@public.gmane.org>,
	netdev <netdev@vger.kernel.org>,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 5/5] sunrpc/auth_gss: Call rcu_barrier() on module unload.
Date: Mon, 8 Jun 2009 21:48:54 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0906082128240.1180@ask.diku.dk> (raw)
In-Reply-To: <1244480449.5040.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>


(trimmed Cc)

On Mon, 8 Jun 2009, Trond Myklebust wrote:

> Hmm... If this is about ensuring that all the call_rcu() callbacks
> complete before we remove the module, then don't we also need similar
> barriers in

Well, Trond that was a hard question, as I don't know this code... but if 
it uses call_rcu() callbacks its most likely.

I have not done a complete sweep of the tree, I have only looked at the 
netdev parts, as this is where I usually snoop around.  So there is 
probably plenty of work for some kernel-janitors (Cc'ing the list ;-))

> net/sunrpc/sunrpc_syms.c:cleanup_sunrpc()

Looking at the code that end up in sunrpc.ko, I see that both 
net/sunrpc/auth_unix.c and net/sunrpc/auth_generic.c uses call_rcu() 
callbacks.

> and in fs/nfs/inode.c:exit_nfs_fs()?

Looking at the code which end up into nfs.ko (which includes 
fs/nfs/inode.c) I see that the fs/nfs/delegation.c uses call_rcu() 
callbacks.

But its hard for me to figure out how this code interacts.  Don't know if 
we need to document a code path that can occur fast enough, before we add 
this safe guard?  It should be Paul's saying...

Cheers,
   Jesper Brouer

--
-------------------------------------------------------------------
MSc. Master of Computer Science
Dept. of Computer Science, University of Copenhagen
Author of http://www.adsl-optimizer.dk
-------------------------------------------------------------------

  parent reply	other threads:[~2009-06-08 19:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 13:11 [PATCH 0/5] We must use rcu_barrier() on module unload Jesper Dangaard Brouer
2009-06-08 13:11 ` [PATCH 1/5] 8021q: Vlan driver should use rcu_barrier() on unload instead of syncronize_net() Jesper Dangaard Brouer
2009-06-08 15:54   ` Paul E. McKenney
2009-06-08 13:11 ` [PATCH 2/5] nfnetlink_queue: Use rcu_barrier() on module unload Jesper Dangaard Brouer
2009-06-08 16:05   ` Paul E. McKenney
2009-06-10  5:38   ` Andrew Morton
2009-06-08 13:11 ` [PATCH 3/5] can: af_can.c use " Jesper Dangaard Brouer
2009-06-08 13:24   ` Oliver Hartkopp
2009-06-10  8:10     ` David Miller
2009-06-10 10:02       ` Alan Cox
2009-06-10 11:33       ` Jan Engelhardt
2009-06-08 16:13   ` Paul E. McKenney
2009-06-08 17:00     ` Oliver Hartkopp
2009-06-08 13:11 ` [PATCH 4/5] sctp: protocol.c call rcu_barrier() on unload Jesper Dangaard Brouer
2009-06-08 16:22   ` Paul E. McKenney
2009-06-09 15:44     ` Vlad Yasevich
2009-06-09 15:50       ` Paul E. McKenney
2009-06-09 16:26         ` Vlad Yasevich
2009-06-08 13:11 ` [PATCH 5/5] sunrpc/auth_gss: Call rcu_barrier() on module unload Jesper Dangaard Brouer
2009-06-08 16:26   ` Paul E. McKenney
2009-06-08 17:00     ` Trond Myklebust
     [not found]       ` <1244480449.5040.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-08 19:48         ` Jesper Dangaard Brouer [this message]
2009-06-08 21:13           ` Paul E. McKenney
2009-06-08 14:00 ` [PATCH 0/5] We must use " Patrick McHardy
2009-06-10  8:11 ` 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=Pine.LNX.4.64.0906082128240.1180@ask.diku.dk \
    --to=hawk@diku.dk \
    --cc=Trond.Myklebust@netapp.com \
    --cc=hawk-4UpuNZONu4c@public.gmane.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox