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 EB251C73C53 for ; Tue, 9 Jul 2019 19:13:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C7D852073D for ; Tue, 9 Jul 2019 19:13:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562699599; bh=kDcSbNV3zUHCWGgMuoqYR+UpXm9UjCOca3wxvegVj0U=; h=Date:From:To:Cc:Subject:List-ID:From; b=ep2DrXZGk/hwodqVdpr8kGne51ZkPHli7go0WpmqirccwSY97AIX37joQsX6GO4s5 gKD0fVhod+58rgsO1E9FudfJxltWK87XwKVYsZ6wV5qqB+MjhQjCRsv1gWZoOLa6O0 HGrX4HvwCuuJCa2ZMFxbulXmbXAPrq+vhurpqseE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729091AbfGITNS (ORCPT ); Tue, 9 Jul 2019 15:13:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:44648 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726335AbfGITNS (ORCPT ); Tue, 9 Jul 2019 15:13:18 -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 70BD420693; Tue, 9 Jul 2019 19:13:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562699597; bh=kDcSbNV3zUHCWGgMuoqYR+UpXm9UjCOca3wxvegVj0U=; h=Date:From:To:Cc:Subject:From; b=QF8PxI8V/joCRGDbEsVwPccQXWyJ5hjc7cTZYa5NfFsAQZugmSK9IhLRhVSr8SC9d cSfgGKieaamuEps8aw7BG/OtffbFbmihclYxiHEaDfxeb6hODrJdfpGlmKPG/r+a0f KFOdOQjYlGqpLUw04Dw/DwfHCx2cTcy/mBb67VRE= Date: Tue, 9 Jul 2019 12:13:16 -0700 From: Eric Biggers To: cgroups@vger.kernel.org, Tejun Heo , Li Zefan , Johannes Weiner Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Reminder: 1 open syzbot bug in "kernel/cgroup" subsystem Message-ID: <20190709191316.GD641@sol.localdomain> Mail-Followup-To: cgroups@vger.kernel.org, Tejun Heo , Li Zefan , Johannes Weiner , 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: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@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 "kernel/cgroup" 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 "kernel/cgroup" 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 cgroup_apply_control_enable Last occurred: 9 days ago Reported: 365 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=4cb6430631b7567848a6736be59d0350b3ada2ea Original thread: https://lkml.kernel.org/lkml/00000000000009f9a305708faf46@google.com/T/#u This bug has a C 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+5493b2a54d31d6aea629@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/00000000000009f9a305708faf46@google.com