Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Greg KH <gregkh@linuxfoundation.org>,
	Alexander Aring <aahringo@redhat.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Alexander Aring <alex.aring@gmail.com>,
	linux-wpan - ML <linux-wpan@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Network Development <netdev@vger.kernel.org>,
	David Girault <david.girault@qorvo.com>,
	Romuald Despres <romuald.despres@qorvo.com>,
	Frederic Blain <frederic.blain@qorvo.com>,
	Nicolas Schodet <nico@ni.fr.eu.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] net: mac802154: Fix a condition in the receive path
Date: Mon, 29 Aug 2022 10:38:21 +0200	[thread overview]
Message-ID: <cbd7d863-4e30-a617-e751-57be0da8706c@datenfreihafen.org> (raw)
In-Reply-To: <YwxOc+X7VpMhKv+4@kroah.com>


Hello Greg.

On 29.08.22 07:28, Greg KH wrote:
> On Sun, Aug 28, 2022 at 08:16:20PM -0400, Alexander Aring wrote:
>> Hi,
>>
>> On Fri, Aug 26, 2022 at 10:31 AM Miquel Raynal
>> <miquel.raynal@bootlin.com> wrote:
>>>
>>> Upon reception, a packet must be categorized, either it's destination is
>>> the host, or it is another host. A packet with no destination addressing
>>> fields may be valid in two situations:
>>> - the packet has no source field: only ACKs are built like that, we
>>>    consider the host as the destination.
>>> - the packet has a valid source field: it is directed to the PAN
>>>    coordinator, as for know we don't have this information we consider we
>>>    are not the PAN coordinator.
>>>
>>> There was likely a copy/paste error made during a previous cleanup
>>> because the if clause is now containing exactly the same condition as in
>>> the switch case, which can never be true. In the past the destination
>>> address was used in the switch and the source address was used in the
>>> if, which matches what the spec says.
>>>
>>> Cc: stable@vger.kernel.org
>>> Fixes: ae531b9475f6 ("ieee802154: use ieee802154_addr instead of *_sa variants")
>>> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>>> ---
>>>   net/mac802154/rx.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/net/mac802154/rx.c b/net/mac802154/rx.c
>>> index b8ce84618a55..c439125ef2b9 100644
>>> --- a/net/mac802154/rx.c
>>> +++ b/net/mac802154/rx.c
>>> @@ -44,7 +44,7 @@ ieee802154_subif_frame(struct ieee802154_sub_if_data *sdata,
>>>
>>>          switch (mac_cb(skb)->dest.mode) {
>>>          case IEEE802154_ADDR_NONE:
>>> -               if (mac_cb(skb)->dest.mode != IEEE802154_ADDR_NONE)
>>> +               if (hdr->source.mode != IEEE802154_ADDR_NONE)
>>>                          /* FIXME: check if we are PAN coordinator */
>>>                          skb->pkt_type = PACKET_OTHERHOST;
>>>                  else
>>
>>
>> This patch looks okay but it should not be addressed to stable. Leave
>> of course the fixes tag.
> 
> Why do that?  Do you not want this in the stable tree?

We want and we will leave the cc to stable in place, see below.

>> Wpan sends pull requests to net and they have their own way to get
>> into the stable tree when they are in net.
> 
> No, the normal method has been used for quite a while now.

I think Alex was refering to the times where netdev core changes have 
been brought to stable via a different route by DaveM.

This was never the case for ieee802154 though. We are such a small 
subsystem with little traffic that we followed the normal stable process 
and our patches ahve always been picked up by Sasha and the bots.

I will take this through my tree with stable cc and fixes tag preserved 
and it will go to Linux via net and follow the normal process.

regards
Stefan Schmidt

  reply	other threads:[~2022-08-29  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 14:29 [PATCH] net: mac802154: Fix a condition in the receive path Miquel Raynal
2022-08-29  0:16 ` Alexander Aring
2022-08-29  5:28   ` Greg KH
2022-08-29  8:38     ` Stefan Schmidt [this message]
2022-08-29  8:52 ` Stefan Schmidt
2022-08-29  9:01   ` Miquel Raynal
2022-08-29  9:04     ` 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=cbd7d863-4e30-a617-e751-57be0da8706c@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --cc=aahringo@redhat.com \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=david.girault@qorvo.com \
    --cc=edumazet@google.com \
    --cc=frederic.blain@qorvo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=nico@ni.fr.eu.org \
    --cc=pabeni@redhat.com \
    --cc=romuald.despres@qorvo.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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