All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Yi Yang <yang.y.yi@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Matt Helsley <matthltc@us.ibm.com>
Subject: Re: [2.6.16 PATCH] Filesystem Events Connector v4
Date: Tue, 28 Mar 2006 16:35:49 +0400	[thread overview]
Message-ID: <20060328123549.GA22116@2ka.mipt.ru> (raw)
In-Reply-To: <44293A5B.3090604@gmail.com>

On Tue, Mar 28, 2006 at 09:30:03PM +0800, Yi Yang (yang.y.yi@gmail.com) wrote:
> Evgeniy Polyakov 写道:

> >>--- a/drivers/connector/connector.c.orig	2006-03-27 
> >>21:35:15.000000000 +0800
> >>+++ b/drivers/connector/connector.c	2006-03-27 21:35:53.000000000 +0800
> >>@@ -111,9 +111,7 @@ int cn_netlink_send(struct cn_msg *msg, 
> >> 
> >> 	NETLINK_CB(skb).dst_group = group;
> >> 
> >>-	netlink_broadcast(dev->nls, skb, 0, group, gfp_mask);
> >>-
> >>-	return 0;
> >>+	return (netlink_broadcast(dev->nls, skb, 0, group, gfp_mask));
> >> 
> >> nlmsg_failure:
> >> 	kfree_skb(skb);
> >>    
> >
> >This error value is propageted back in current connector code already.
> >  
> Which version of kernel do you mean? for 2.6.16, it doesn't return 
> netlink_broadcast's return value.

It was committeed in 2.6.17 timeframe.
b191ba0d599928372be5a89f75486eb58efab48a commit id.

It also includes new netlink_has_listeners() call usage, which allows to
check in advance if there are listeners or not for given netlink group.
netlink_has_listeners() can return false positives, which will be caught
by netlink_broadcast().

-- 
	Evgeniy Polyakov

      reply	other threads:[~2006-03-28 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 15:05 [2.6.16 PATCH] Filesystem Events Connector v4 Yi Yang
2006-03-28  7:51 ` Evgeniy Polyakov
2006-03-28 13:30   ` Yi Yang
2006-03-28 12:35     ` Evgeniy Polyakov [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=20060328123549.GA22116@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=yang.y.yi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.