From: Patrick McHardy <kaber@trash.net>
To: Julius Volz <juliusv@google.com>
Cc: 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 14:15:49 +0200 [thread overview]
Message-ID: <4875FD75.1090107@trash.net> (raw)
In-Reply-To: <f4845fc0807091116s58b0b492p9f28281fcdca4e17@mail.gmail.com>
Julius Volz wrote:
> On Wed, Jul 9, 2008, Patrick McHardy wrote:
>>> +static int ip_vs_genl_set_cmd(struct sk_buff *skb, struct genl_info
>>> *info)
>>> +{
>>> + struct ip_vs_service *svc;
>>> + struct ip_vs_service_user usvc;
>>> + struct ip_vs_dest_user udest;
>>> + int ret = 0, cmd, flags;
>>> + int need_full_svc = 0, need_full_dest = 0;
>>> +
>>> + cmd = info->genlhdr->cmd;
>>> + flags = info->nlhdr->nlmsg_flags;
>>> +
>>> + /* increase the module use count */
>>> + ip_vs_use_count_inc();
>> This looks fishy - the reference probably must be taken by
>> genetlink before calling the command handler.
>
> That would seem better, but is that possible? I took this from the
> sockopt interface. What would you generally want to do in this
> situation?
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.
next prev parent reply other threads:[~2008-07-10 12:15 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 [this message]
2008-07-10 13:58 ` Julius Volz
2008-07-10 14:43 ` Thomas Graf
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=4875FD75.1090107@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=juliusv@google.com \
--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).