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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=unavailable 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 94141C10F14 for ; Thu, 11 Apr 2019 00:50:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5C44C20663 for ; Thu, 11 Apr 2019 00:50:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=themaw.net header.i=@themaw.net header.b="QKJZTDNP"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="DdZP7Qg6" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726728AbfDKAuY (ORCPT ); Wed, 10 Apr 2019 20:50:24 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:51257 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725782AbfDKAuX (ORCPT ); Wed, 10 Apr 2019 20:50:23 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 29BC321687; Wed, 10 Apr 2019 20:50:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 10 Apr 2019 20:50:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=themaw.net; h= message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; s=fm2; bh= VNHzEkSAdnkBEisVXTY5QDMcCIK0gyWcq96ri9B6hJU=; b=QKJZTDNPQx1s6x/q 7BVe+B3lCq/uPu9Ot1CoyhoJlyAtmquVrzoxdv5kWP/zUHbiK7RSi9gy7eIAXT1n oS3QzKyB3UOn/z/7Q0/GwHqpS41VVjOuCLp2RqYkvNBCAgZUFIufVpLja9sW+CnH 8sKThxuSmoEcomEkVVsBYuiyNa8wXDqJw2hvVdomZwTNHxNLvnJmuR5/oPNJ6oG6 FKM3etkKj/fdbW1I+w1xb9NK18+Eyd0EojLUxPN1GVWYHR4+we5ob/c2iTD2Ec2a Sl5CDtJzS+zmePVVj/GAjtYkBlpHpfK5/V5LOm5LtVsfgDIh2S1KCbIGRpI6PK9d oxlkIA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=VNHzEkSAdnkBEisVXTY5QDMcCIK0gyWcq96ri9B6h JU=; b=DdZP7Qg65f85ykJuw66rWNPvQ+FmDo+NMEwvYgt4w8UeZaCoJ3rTkjNrP oyuRR5W9MAWg8TGR0mItI4QO3gNJdYlDPAu15zfSUTueaWN+jnk9umbxRVvd0doq eGFbSUH2aUzvnBFIknfzWhdBTAvAXSBdvBpozyzveDeXTdgI6yVqrLmWnZe+EvcL 26NtNYRcjuYCiKJS/NS4sEBWX6hELdR6QH39LqPBqaO34MUMwBBDlOqg6s2JAOoU /gXiMqynVz0z83mGakFrx8lPb/krA/6tRsFNQ1BQD4q5ZmveUJhlahwd3nIMUnn9 SV0091nOwR+B8oaPncYu00957SvPw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudekgdefgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkuffhvfffjghftgfoggfgsehtjeertdertdejnecuhfhrohhmpefkrghnucfm vghnthcuoehrrghvvghnsehthhgvmhgrfidrnhgvtheqnecukfhppeduudekrddvtdekrd eifedrvdefvdenucfrrghrrghmpehmrghilhhfrhhomheprhgrvhgvnhesthhhvghmrgif rdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from pluto.themaw.net (unknown [118.208.63.232]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B5FCE407B; Wed, 10 Apr 2019 20:50:21 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pluto.themaw.net (Postfix) with ESMTP id BA4861C0117; Thu, 11 Apr 2019 08:50:17 +0800 (AWST) Message-ID: Subject: Re: kernel BUG at fs/inode.c:LINE! From: Ian Kent To: Dmitry Vyukov , Al Viro Cc: syzbot , Andrew Morton , Amir Goldstein , linux-fsdevel , LKML , Tetsuo Handa , syzkaller-bugs Date: Thu, 11 Apr 2019 08:50:17 +0800 In-Reply-To: References: <00000000000051e9c2057d31a563@google.com> <00000000000036a4a9058619dff3@google.com> <20190410002603.GS2217@ZenIV.linux.org.uk> <5c581e6eadc946b965e3138c9daffda75b1fba56.camel@themaw.net> <1f1d3b95189b6b8acfdf61dd05a804744791d313.camel@themaw.net> <20190410121159.GY2217@ZenIV.linux.org.uk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, 2019-04-10 at 14:41 +0200, Dmitry Vyukov wrote: > On Wed, Apr 10, 2019 at 2:12 PM Al Viro wrote: > > > > On Wed, Apr 10, 2019 at 08:07:15PM +0800, Ian Kent wrote: > > > > > > I'm unable to find a branch matching the line numbers. > > > > > > > > Given that, on the face of it, the scenario is impossible I'm > > > > seeking clarification on what linux-next to look at for the > > > > sake of accuracy. > > > > > > > > So I'm wondering if this testing done using the master branch > > > > or one of the daily branches one would use to check for conflicts > > > > before posting? > > > > > > Sorry those are tags not branches. > > > > FWIW, that's next-20181214; it is what master had been in mid-December > > and master is rebased every day. Can it be reproduced with the current > > tree? > > From the info on the dashboard we know that it happened only once on > d14b746c (the second one is result of reproducing the first one). So > it was either fixed or just hard to trigger. Looking at the source of tag next-20181214 in linux-next-history I see this is mistake I made due to incorrect error handling which I fixed soon after (there was in fact a double iput()). I'm pretty sure this never made it to a released kernel so unless there's a report of this in a stable released kernel I'm going to move on. Thanks Ian