From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A217AC76186 for ; Wed, 24 Jul 2019 02:52:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 79F53229F6 for ; Wed, 24 Jul 2019 02:52:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563936758; bh=/GvI7a0xWcKOYjJIwmdjPjVkfTHbx5dcodTV315L1XE=; h=Date:From:To:Cc:Subject:List-ID:From; b=DAYjXQtHqP7tp4IXsm5xNhb+MNkt2PurON67qis6lPC4Q2pDt4LUcwzT66M1drYQt h/MvU/nW/QobrTBw9a2rmYctskOxD5TRz8sFkGZEu9S8eQpBnPz2fEeEVGMP5VQfCk yfMPaAXzJNdMq43OIqUOZaZL329ewO0EshJg84IA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726396AbfGXCwf (ORCPT ); Tue, 23 Jul 2019 22:52:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:47730 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725827AbfGXCwf (ORCPT ); Tue, 23 Jul 2019 22:52:35 -0400 Received: from sol.localdomain (c-24-5-143-220.hsd1.ca.comcast.net [24.5.143.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 27F892253D; Wed, 24 Jul 2019 02:52:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563936754; bh=/GvI7a0xWcKOYjJIwmdjPjVkfTHbx5dcodTV315L1XE=; h=Date:From:To:Cc:Subject:From; b=fryLv9ogkE+mxRdWGoh8W1UnH40oFAiw9vPJ+EEQnP9dceGtffVXQxOpy56cJU8KJ pVGjyB9NpmC8yreWTM3cWrMwhPcvpNHt4mkmaVi4jrPwyk+g9WjSviMDzUYXkhuXIs oWel4q5R9noFGZ7JJzPWp/x0d2aZsuOylaSGMpQE= Date: Tue, 23 Jul 2019 19:52:32 -0700 From: Eric Biggers To: netdev@vger.kernel.org, Steffen Klassert , Herbert Xu , "David S. Miller" Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Reminder: 1 open syzbot bug in "net/pfkey" subsystem Message-ID: <20190724025232.GP643@sol.localdomain> Mail-Followup-To: netdev@vger.kernel.org, Steffen Klassert , Herbert Xu , "David S. Miller" , linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.12.1 (2019-06-15) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org [This email was generated by a script. Let me know if you have any suggestions to make it better, or if you want it re-generated with the latest status.] Of the currently open syzbot reports against the upstream kernel, I've manually marked 1 of them as possibly being a bug in the "net/pfkey" subsystem. If you believe this bug is no longer valid, please close the syzbot report by sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the original thread, as explained at https://goo.gl/tpsmEJ#status If you believe I misattributed this bug to the "net/pfkey" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here is the bug: -------------------------------------------------------------------------------- Title: WARNING in pfkey_sock_destruct Last occurred: 168 days ago Reported: 300 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=6dc52e859d5ccc5fdce168973ab63b97ac7e41ba Original thread: https://lkml.kernel.org/lkml/0000000000002b8eb70576c15840@google.com/T/#u Unfortunately, this bug does not have a reproducer. No one replied to the original thread for this bug. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+4acf0d9092f91bb60431@syzkaller.appspotmail.com If you send any email or patch for this bug, please consider replying to the original thread. For the git send-email command to use, or tips on how to reply if the thread isn't in your mailbox, see the "Reply instructions" at https://lkml.kernel.org/r/0000000000002b8eb70576c15840@google.com