On Tue, Apr 13, 2021 at 3:10 PM Gong, Sishuai wrote:
>
> Hi,
>
> We found a concurrency bug in linux 5.12-rc3 and we are able to reproduce it
> under x86. This bug happens when two l2tp functions l2tp_tunnel_register()
> and l2tp_xmit_core() are running in parallel. In general,
> l2tp_tunnel_re
On Apr 14, 2021, at 3:37 PM, Tom Parkin wrote:
>
> On Tue, Apr 13, 2021 at 17:30:17 +, Gong, Sishuai wrote:
>> Hi,
>>
>> We found a concurrency bug in linux 5.12-rc3 and we are able to reproduce it
>> under x86. This bug happens when two l2tp functions l2tp_tunnel_register()
>> and l2tp_x
On Tue, Apr 13, 2021 at 17:30:17 +, Gong, Sishuai wrote:
> Hi,
>
> We found a concurrency bug in linux 5.12-rc3 and we are able to reproduce it
> under x86. This bug happens when two l2tp functions l2tp_tunnel_register()
> and l2tp_xmit_core() are running in parallel. In general,
> l2tp_tu
Hi,
We found a concurrency bug in linux 5.12-rc3 and we are able to reproduce it
under x86. This bug happens when two l2tp functions l2tp_tunnel_register() and
l2tp_xmit_core() are running in parallel. In general, l2tp_tunnel_register()
registered a tunnel that hasn’t been fully initialized and