From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next v2 01/16] l2tp: update sk_user_data while holding sk_callback_lock Date: Mon, 12 Feb 2018 11:21:29 -0500 (EST) Message-ID: <20180212.112129.1458610223636502379.davem@davemloft.net> References: <1518430280-16671-1-git-send-email-jchapman@katalix.com> <1518430280-16671-2-git-send-email-jchapman@katalix.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, kbuild-all@01.org To: jchapman@katalix.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:54418 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964875AbeBLQVa (ORCPT ); Mon, 12 Feb 2018 11:21:30 -0500 In-Reply-To: <1518430280-16671-2-git-send-email-jchapman@katalix.com> Sender: netdev-owner@vger.kernel.org List-ID: From: James Chapman Date: Mon, 12 Feb 2018 10:11:05 +0000 > Since L2TP hooks on sockets opened by userspace using sk_user_data, we > may race with other socket families that attempt to use the same > socket. > > This problem was discovered by syzbot using AF_KCM. KCM has since been > modified to use only TCP sockets to avoid hitting this issue but we > should prevent such races in L2TP anyway. > > Fixes: c8fffcea0a079 ("l2tp: Refactor l2tp core driver to make use of the common UDP tunnel function") > Reported-by: syzbot+8865eaff7f9acd593945@syzkaller.appspotmail.com Yikes. Where is your signoff James? > Kernel BUG at net/l2tp/l2tp_ppp.c:176! > invalid opcode: 0000 [#1] SMP KASAN > Dumping ftrace buffer: > (ftrace buffer empty) And this oops dump should be before the various fixes/reported-by/signed-off-by tags. Thanks.