Re: [PATCH v2] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig

[Michael Bommarito]

On Wed, May 20, 2026 at 11:19 AM Luiz Augusto von Dentz
<luiz.dentz@xxxxxxxxx> wrote:
> This coming from the spec is priceless because silently discarding the
> packets means the remote stack won't know the responses were
> discarded, causing the stacks to go out of sync. We also shouldn't
> process packets beyond the allowed MTU. Therefore, I strongly disagree
> with the spec requiring an identifier on the reject, as this implies
> that even if a custom MTU is set, the packet must still be processed
> if it exceeds that MTU to find the first request command within it.

Should I keep a verbose comment string about this rationale in the
next version?  This seems like something that might trigger questions
in the future if there are issues between Linux <-> noisy/buggy
stacks.

Thanks,
Mike