lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 3 Sep 2020 11:11:06 -0700
From:   Cong Wang <>
To:     Eric Dumazet <>
Cc:     syzbot <>,
        David Miller <>,
        Jamal Hadi Salim <>,
        Jiri Pirko <>,
        Jakub Kicinski <>,
        LKML <>,
        Linux Kernel Network Developers <>,
        syzkaller-bugs <>
Subject: Re: INFO: task hung in tcf_ife_init

On Thu, Sep 3, 2020 at 2:47 AM Eric Dumazet <> wrote:
> This commit might be related :
> commit 4e407ff5cd67ec76eeeea1deec227b7982dc7f66
> Author: Cong Wang <>
> Date:   Sun Aug 19 12:22:12 2018 -0700
>     act_ife: move tcfa_lock down to where necessary

It does not look like my commit's fault. From my _quick_ understanding
of this problem, we somehow have a "deadlock" situation:

Thread A allocates an IDR with a specific index and calls populate_metalist()
to re-accquire the RTNL lock.

Thread B gets RTNL lock right after thread A releases it, then it waits for
thread A to finally commit the IDR change.


Powered by blists - more mailing lists