From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752783AbeA3N7g (ORCPT <rfc822;w@1wt.eu>);
        Tue, 30 Jan 2018 08:59:36 -0500
Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:41452 "EHLO
        Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1751711AbeA3N7f (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 30 Jan 2018 08:59:35 -0500
Date: Tue, 30 Jan 2018 14:56:43 +0100
From: Florian Westphal <fw@strlen.de>
To: syzbot <syzbot+a4c2dc980ac1af699b36@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
        syzkaller-bugs@googlegroups.com
Subject: Re: possible deadlock in do_ipv6_setsockopt
Message-ID: <20180130135643.GL5906@breakpoint.cc>
References: <001a11433beebd52530563c84419@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001a11433beebd52530563c84419@google.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

#syz dup: possible deadlock in do_ip_getsockopt