lists.openwall.net   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  linux-cve-announce  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]
Message-Id: <20180219.143829.842027434381717638.davem@davemloft.net>
Date:   Mon, 19 Feb 2018 14:38:29 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     pabeni@...hat.com
Cc:     netdev@...r.kernel.org, jon.maloy@...csson.com,
        ying.xue@...driver.com
Subject: Re: [PATCH net-next] tipc: don't call sock_release() in atomic
 context

From: Paolo Abeni <pabeni@...hat.com>
Date: Mon, 19 Feb 2018 19:02:24 +0100

> syzbot reported a scheduling while atomic issue at netns
> destruction time:
 ...
> This is caused by tipc_topsrv_stop() releasing the listener socket
> with the idr lock held. This changeset addresses the issue moving
> the release operation outside such lock.
> 
> Reported-and-tested-by: syzbot+749d9d87c294c00ca856@...kaller.appspotmail.com
> Fixes: 0ef897be12b8 ("tipc: separate topology server listener socket from subcsriber sockets")
> Signed-off-by: Paolo Abeni <pabeni@...hat.com>

Applied, thanks Paolo.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ