All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <alex.aring@gmail.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH bluetooth-next 4/4] mac802154: use atomic ops for sequence incrementation
Date: Fri, 22 May 2015 14:33:54 +0200	[thread overview]
Message-ID: <555F2232.50500@osg.samsung.com> (raw)
In-Reply-To: <20150522121238.GA748@omega>

Hello.

On 22/05/15 14:12, Alexander Aring wrote:
> On Fri, May 22, 2015 at 12:34:19PM +0200, Marc Kleine-Budde wrote:
>> On 05/22/2015 12:30 PM, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> On 22/05/15 10:59, Marc Kleine-Budde wrote:
>>>> On 05/22/2015 10:57 AM, Alexander Aring wrote:
>>>>> This patch will use atomic operations for sequence number incrementation
>>>>> while MAC header generation. Upper layers like af_802154 or 6LoWPAN
>>>>> could call this function in a parallel context while generating 802.15.4
>>>>> MAC header before queuing into wpan interfaces transmit queue.
>>>> what about swapping patch 3 and 4?
>>> To avoid having problems during a git bisect later one? E.g. having the
>>> lock removed but no atomic in place?
>> Yes, that's what I was thinking about. I don't know the code to tell if
>> this is an issue here.
>>
> The problem is more difficult because the dsn incrementation which I do
> atomic now had never a locking mechanism. So this was always not working
> correctly. Somebody need to scream now "hey fix that in net, not next".

Hey, fix that in net not next! :P

If we know it causes problems in current net we should indeed try to 
submit it there.
Given it is only a few lines it might be worth the effort even now. Some 
people might be using kernel releases for their work and thus they could 
get this fix one release (3 months) earlier.

> I do at the moment only critical things fixed in net, like [0].
>
Sure, these are the most important ones. I leave it to you to decide if 
you think this one is worth the extra effort.

> But we should swap it because I first wrote some "TODO we should use
> atomic here" and then later I decide to implement this TODO. At the end
> this results in some cherry-pick orgy and I did not change it.
>
ok, cool.

regards
Stefan Schmidt

  reply	other threads:[~2015-05-22 12:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  8:57 [PATCH bluetooth-next 0/4] mac802154: remove pib/mib locks and locking fixes Alexander Aring
2015-05-22  8:57 ` [PATCH bluetooth-next 1/4] mac802154: fix hold rtnl while ioctl Alexander Aring
2015-05-22 12:15   ` Stefan Schmidt
2015-05-22  8:57 ` [PATCH bluetooth-next 2/4] mac802154: remove pib lock Alexander Aring
2015-05-22 12:19   ` Stefan Schmidt
2015-05-22 12:41     ` Alexander Aring
2015-05-22 12:48       ` Stefan Schmidt
2015-05-22  8:57 ` [PATCH bluetooth-next 3/4] mac802154: remove mib lock Alexander Aring
2015-05-22 12:25   ` Stefan Schmidt
2015-05-22  8:57 ` [PATCH bluetooth-next 4/4] mac802154: use atomic ops for sequence incrementation Alexander Aring
2015-05-22  8:59   ` Marc Kleine-Budde
2015-05-22 10:30     ` Stefan Schmidt
2015-05-22 10:34       ` Marc Kleine-Budde
2015-05-22 10:40         ` Stefan Schmidt
2015-05-22 12:12         ` Alexander Aring
2015-05-22 12:33           ` Stefan Schmidt [this message]
2015-05-22 12:27   ` Stefan Schmidt

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=555F2232.50500@osg.samsung.com \
    --to=stefan@osg.samsung.com \
    --cc=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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.