All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215681] Malicious advertising data showed in dmesg
Date: Wed, 16 Mar 2022 16:55:22 +0000	[thread overview]
Message-ID: <bug-215681-62941-auOFyYIZ3R@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215681-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215681

--- Comment #2 from Olivier JUDITH (gnulux@gmail.com) ---


Hi, 

Yes i compiled before and i can do it again. 
In the meanwhile i tried 5.15 and i've no Malicious messages displayed.

i'll we apply you suggestion

The issue come from hci_le_adv_report_evt in hci_event.h. i noticed that this
function is a bit different in 5.15. 

i also understood that the change was to evict flow of messages but the real
cause seems to be a packet size is exceeded. Does this mean that my advertising
is not correct ?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2022-03-16 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 15:35 [Bug 215681] New: Malicious advertising data showed in dmesg bugzilla-daemon
2022-03-15 15:41 ` [Bug 215681] " bugzilla-daemon
2022-03-16 16:55 ` bugzilla-daemon [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=bug-215681-62941-auOFyYIZ3R@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@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.