public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Skalski <l.skalski@samsung.com>
To: Sergei Zviagintsev <sergei@s15v.net>
Cc: gregkh@linuxfoundation.org, daniel@zonque.org,
	dh.herrmann@gmail.com, tixxdz@opendz.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdbus: do not append the same connection to the queue twice
Date: Tue, 14 Apr 2015 10:27:37 +0200	[thread overview]
Message-ID: <552CCF79.4050903@samsung.com> (raw)
In-Reply-To: <20150413214834.GE8500@localhost.localdomain>


On 04/13/2015 11:48 PM, Sergei Zviagintsev wrote:
> Hi Lukasz,
> 

Hi,

> On Mon, Apr 13, 2015 at 04:14:06PM +0200, Lukasz Skalski wrote:
>> As it was discussed on systemd ML [1], the same connection should be
>> queued up only once for a given well-known name.
>>
>> [1] http://lists.freedesktop.org/archives/systemd-devel/2015-April/030494.html
>>
>> Signed-off-by: Lukasz Skalski <l.skalski@samsung.com>
>>
>> diff --git a/ipc/kdbus/names.c b/ipc/kdbus/names.c
>> index 657008e..a546a84 100644
>> --- a/ipc/kdbus/names.c
>> +++ b/ipc/kdbus/names.c
>> @@ -353,10 +353,23 @@ int kdbus_name_acquire(struct kdbus_name_registry *reg,
>>  	} else if (flags & KDBUS_NAME_QUEUE) {
>>  		/* add to waiting-queue of the name */
>>  
>> -		ret = kdbus_name_pending_new(e, conn, flags);
>> -		if (ret >= 0)
>> -			/* tell the caller that we queued it */
>> -			rflags |= KDBUS_NAME_IN_QUEUE;
>> +		struct kdbus_name_pending *p;
>> +		bool in_queue = false;
>> +
>> +		list_for_each_entry(p, &e->queue, name_entry) {
>> +			if (p->conn == conn) {
>> +				/* connection is already queued */
>> +				rflags |= KDBUS_NAME_IN_QUEUE;
>> +				in_queue = true;
> 
> break here?
> 

Right. I've just sent v2. Thanks!

>> +			}
>> +		}
>> +
>> +		if (!in_queue) {
>> +			ret = kdbus_name_pending_new(e, conn, flags);
>> +			if (ret >= 0)
>> +				/* tell the caller that we queued it */
>> +				rflags |= KDBUS_NAME_IN_QUEUE;
>> +		}
>>  	} else {
>>  		/* the name is busy, return a failure */
>>  		ret = -EEXIST;
>> -- 
>> 1.9.3
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
> 

Cheers,
-- 
Lukasz Skalski
Samsung R&D Institute Poland
Samsung Electronics
l.skalski@samsung.com

      reply	other threads:[~2015-04-14  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 14:14 [PATCH] kdbus: do not append the same connection to the queue twice Lukasz Skalski
2015-04-13 21:48 ` Sergei Zviagintsev
2015-04-14  8:27   ` Lukasz Skalski [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=552CCF79.4050903@samsung.com \
    --to=l.skalski@samsung.com \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergei@s15v.net \
    --cc=tixxdz@opendz.org \
    /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