On 4/14/21 6:52 PM, Eric Dumazet wrote:
>
>
> On 4/14/21 1:27 AM, Willem de Bruijn wrote:
>> On Tue, Apr 13, 2021 at 6:55 PM Xie He wrote:
>>>
>>> On Tue, Apr 13, 2021 at 1:51 PM Gong, Sishuai wrote:
Hi,
We found a data race in linux-5.12-rc3 between af_packet.c functions
On 4/14/21 1:27 AM, Willem de Bruijn wrote:
> On Tue, Apr 13, 2021 at 6:55 PM Xie He wrote:
>>
>> On Tue, Apr 13, 2021 at 1:51 PM Gong, Sishuai wrote:
>>>
>>> Hi,
>>>
>>> We found a data race in linux-5.12-rc3 between af_packet.c functions
>>> fanout_demux_rollover() and __fanout_unlink() and
On Tue, Apr 13, 2021 at 6:55 PM Xie He wrote:
>
> On Tue, Apr 13, 2021 at 1:51 PM Gong, Sishuai wrote:
> >
> > Hi,
> >
> > We found a data race in linux-5.12-rc3 between af_packet.c functions
> > fanout_demux_rollover() and __fanout_unlink() and we are able to reproduce
> > it under x86.
> >
>
On Tue, Apr 13, 2021 at 1:51 PM Gong, Sishuai wrote:
>
> Hi,
>
> We found a data race in linux-5.12-rc3 between af_packet.c functions
> fanout_demux_rollover() and __fanout_unlink() and we are able to reproduce it
> under x86.
>
> When the two functions are running together, __fanout_unlink() wi
Hi,
We found a data race in linux-5.12-rc3 between af_packet.c functions
fanout_demux_rollover() and __fanout_unlink() and we are able to reproduce it
under x86.
When the two functions are running together, __fanout_unlink() will grab a lock
and modify some attribute of packet_fanout variable
