All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: "# 3.19.x" <stable@vger.kernel.org>
Subject: False-positive Bluetooth messages fix in stable kernels
Date: Wed, 2 Feb 2022 12:13:19 +0300	[thread overview]
Message-ID: <6ce8dff1-5dcf-b560-5169-47acef139422@gmail.com> (raw)

Dear Greg and Sasha,

can you, please, cherry-pick following commit from Linus' tree:
commit 899663be5e75dc0174dc8bda0b5e6826edf0b29a with subject line 
"Bluetooth: refactor malicious adv data check".

There is missing Fixes: tag inside commit log, which causes this patch 
to not go to stable trees, but it actually fixes false-positive messages 
in dmesg.

I've seen 2 reports and I've asked reporters to test this patch and they 
have reported, that this patch actually fixes the problem [1] (second 
report was private, so I can't refer it there)



[1] 
https://lore.kernel.org/linux-bluetooth/CAC2ZOYuXg4btk9PaE3whmP7JnntsixEvDuBNvv7GL1pvU1nepQ@mail.gmail.com/T/#t





With regards,
Pavel Skripkin

             reply	other threads:[~2022-02-02  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  9:13 Pavel Skripkin [this message]
2022-02-03 17:01 ` False-positive Bluetooth messages fix in stable kernels Greg KH

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=6ce8dff1-5dcf-b560-5169-47acef139422@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=stable@vger.kernel.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 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.