On Mon, 7 Sep 2020 13:00:07 +0700 Hoang Huu Le wrote:
> In the commit fdeba99b1e58
> ("tipc: fix use-after-free in tipc_bcast_get_mode"), we're trying
> to make sure the tipc_net_finalize_work work item finished if it
> enqueued. But calling flush_scheduled_work() is not just affecting
> above wor
-next
tree.
-Original Message-
From: Hoang Huu Le
Sent: Monday, September 7, 2020 2:17 PM
To: Xue, Ying ; netdev@vger.kernel.org
Cc: jma...@redhat.com; ma...@donjonn.com;
syzbot+d5aa7e0385f6a5d0f...@syzkaller.appspotmail.com
Subject: [net-next v2] tipc: fix a deadlock when flushing sche
In the commit fdeba99b1e58
("tipc: fix use-after-free in tipc_bcast_get_mode"), we're trying
to make sure the tipc_net_finalize_work work item finished if it
enqueued. But calling flush_scheduled_work() is not just affecting
above work item but either any scheduled work. This has turned out
to be o
In the commit fdeba99b1e58
("tipc: fix use-after-free in tipc_bcast_get_mode"), we're trying
to make sure the tipc_net_finalize_work work item finished if it
enqueued. But calling flush_scheduled_work() is not just affecting
above work item but either any scheduled work. This has turned out
to be o
