From: Thomas Graf <tgraf@suug.ch>
To: Julius Volz <juliusv@google.com>
Cc: Patrick McHardy <kaber@trash.net>,
netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
vbusam@google.com, horms@verge.net.au, davem@davemloft.net
Subject: Re: [PATCH 2/2] IPVS: Add genetlink interface implementation
Date: Thu, 10 Jul 2008 16:43:08 +0200 [thread overview]
Message-ID: <20080710144308.GV20815@postel.suug.ch> (raw)
In-Reply-To: <f4845fc0807100658i32f7ba5fo2e04ba81fec02eb1@mail.gmail.com>
* Julius Volz <juliusv@google.com> 2008-07-10 15:58
> On Thu, Jul 10, 2008 at 2:15 PM, Patrick McHardy <kaber@trash.net> wrote:
> > There probably should be a struct module *owner in the
> > ops registered with genetlink. This is necessary at
> > least to make sure that modules don't disappear during
> > dumps.
>
> There seems to be no such thing in genetlink. af_netlink.c tracks the
> owner of a netlink socket, but that would increase the use count of
> the genetlink module.
>
> First I would have suspected the genl_mutex to be held while dumping,
> so that at least unregistering the family at module unload would
> block. But the mutex is explicitly unlocked for the duration of the
> netlink dump:
It used to be like before the locking during dumps was revised. I
promised to redo the locking and module owner tracking but haven't
gotten around. Patrick's suggestion certainly makes sense.
> net/netlink/genetlink.c:
>
> genl_unlock();
> err = netlink_dump_start(genl_sock, skb, nlh,
> ops->dumpit, ops->done);
> genl_lock();
>
> Julius
next prev parent reply other threads:[~2008-07-10 14:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 15:11 [PATCH 0/2] IPVS: Add Generic Netlink configuration interface Julius Volz
2008-07-09 15:11 ` [PATCH 1/2] IPVS: Add genetlink interface definitions to ip_vs.h Julius Volz
2008-07-09 15:11 ` [PATCH 2/2] IPVS: Add genetlink interface implementation Julius Volz
2008-07-09 15:17 ` YOSHIFUJI Hideaki / 吉藤英明
2008-07-09 15:24 ` Julius Volz
2008-07-09 16:43 ` Patrick McHardy
2008-07-09 18:16 ` Julius Volz
2008-07-10 12:15 ` Patrick McHardy
2008-07-10 13:58 ` Julius Volz
2008-07-10 14:43 ` Thomas Graf [this message]
2008-07-10 11:20 ` Julius Volz
2008-07-10 11:36 ` Thomas Graf
2008-07-10 12:33 ` Julius Volz
2008-07-10 14:41 ` Thomas Graf
2008-07-10 15:13 ` Julius Volz
2008-07-10 21:16 ` Thomas Graf
2008-07-10 23:16 ` Julius Volz
2008-07-16 12:15 ` Thomas Graf
2008-07-16 13:03 ` Julius Volz
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=20080710144308.GV20815@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=juliusv@google.com \
--cc=kaber@trash.net \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vbusam@google.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;
as well as URLs for NNTP newsgroup(s).