Hi Linus,
On Thu, Aug 5, 2021 at 11:45 AM Linus Torvalds
[off-list ref] wrote:
On Thu, Aug 5, 2021 at 11:19 AM Luiz Augusto von Dentz
[off-list ref] wrote:
quoted
It doesn't apply to bluetooth-next, could you please rebase it.
If you're ok with the patch, I think it should go into 5.14 - and be
marked for stable.
The locking right now is very wrong, and causes syzbot warnings and
probably keeps people from finding other things.
And we can't just revert the incorrect locking change, because it was
a security issue.
So this should go in the current release cycle. I agree it's a bit
scary - not because I think the patch is all that complicated, but
because this area has clearly had issues and is subtle - but I'd
rather do it asap and get reports on it early than delay it further.
Alright so we are skipping bluetooth-next then, I thought of using
bluetooth-next for further testing these changes but I agree this
should go into 5.14 so Im fine if you take it straight to your tree:
Signed-off-by: Luiz Augusto von Dentz <redacted>
--
Luiz Augusto von Dentz