Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp1184952rwb; Tue, 27 Sep 2022 09:28:00 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4y+KDUEA/1F4PxhwmwzrFdq2GE35dKT/efkLSom9cjh+2QMvr7UVmOPyFqhMX7XCukkRRu X-Received: by 2002:a17:907:16a3:b0:783:96fc:7fc0 with SMTP id hc35-20020a17090716a300b0078396fc7fc0mr9072279ejc.441.1664296079921; Tue, 27 Sep 2022 09:27:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664296079; cv=none; d=google.com; s=arc-20160816; b=in3uUpJH2luJo39gM67vZzwkqlzNrAEGbjh/Gp/ad4wclT9dcWawMNOxuIURqcGf3M AQPXhbd0A0qN4d8Ki5C8/WNA1f8kbu4xz5r/JXrpXI46jkq1sjxbWq4/XWtrvsFMsMEb 5PR0awmMc7CBtYKDt6piD1sM7Hwui6cAiqD2e0aG3VyPOzpiH4R8ZklCIbY88HiiOGWL Pnx1FJtQl13l9bUqWm6lWcC6EXZKK8UydrXImNk5UYhIu01ILFp140wRrXH8W4BOQWg3 4y87Xm2AGuciSfZb3pQLRQKEgBeqnvylFiTKgBEBV9gH3hKbYrR/bNAGtoElImF20b5M rNtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date:dkim-signature; bh=ypV3UW9Ng5fQs0wjrGBbcNZZzO1m7OPzcTAT15eflxw=; b=xG4tuxw4d6ne0ualTdkLb3QwVOQrgNO5/J0kqSgYEWrEl1gLuDXnxmMEcQp9naH59y S87bhLTkDfHcfd3xbEnuLlHgbPD6dvbspEDSjq5n0SgX+WyNRWwe9gQWFYK7U+LwNTcO BDtcYsRl7uusl0cHzA51T0fiqKtGed2fBgTUzrzWy5k63YPh6VCsmHMmBfXVmg+vxcel YoZJIT6croGQf7doJslavKJhnHbQg55vHiak59XlUh4VEZP0p46ezSu1vFnwlYYA2oDF PtTdm0esHQVFmC241DBJJGO53a/43oQIbZ/8wmWlSgQ+Oie9JGZAnWoK4JH21vdcVb2g AIVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="Q/HVXL91"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ji19-20020a170907981300b0073317952891si2068361ejc.777.2022.09.27.09.27.33; Tue, 27 Sep 2022 09:27:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="Q/HVXL91"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232988AbiI0QKy (ORCPT + 99 others); Tue, 27 Sep 2022 12:10:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232971AbiI0QK0 (ORCPT ); Tue, 27 Sep 2022 12:10:26 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D7B21D6D0D for ; Tue, 27 Sep 2022 09:09:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664294963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ypV3UW9Ng5fQs0wjrGBbcNZZzO1m7OPzcTAT15eflxw=; b=Q/HVXL91N8tkvYPR7dnSiRxS7VWJKLyeO5lvS6vbRDa0clsyejqQelPJoLItKRTyoKeoIl D3e28lqtLtDBHJ6EE1cZ7jELKZGIOn3/ETxCY5I6XpTGp3tZgs+dX7wPE5L6fKQfmBuD4z DlHkyJw9RgiWnR2+/wrHCK7x2fQo+1Y= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-282-167bo7ufPyGV5maHIpQN6Q-1; Tue, 27 Sep 2022 12:09:19 -0400 X-MC-Unique: 167bo7ufPyGV5maHIpQN6Q-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4837F1C05AEA; Tue, 27 Sep 2022 16:09:19 +0000 (UTC) Received: from file01.intranet.prod.int.rdu2.redhat.com (file01.intranet.prod.int.rdu2.redhat.com [10.11.5.7]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 36ECB492B04; Tue, 27 Sep 2022 16:09:19 +0000 (UTC) Received: from file01.intranet.prod.int.rdu2.redhat.com (localhost [127.0.0.1]) by file01.intranet.prod.int.rdu2.redhat.com (8.14.4/8.14.4) with ESMTP id 28RG9J9g005322; Tue, 27 Sep 2022 12:09:19 -0400 Received: from localhost (mpatocka@localhost) by file01.intranet.prod.int.rdu2.redhat.com (8.14.4/8.14.4/Submit) with ESMTP id 28RG9JgO005318; Tue, 27 Sep 2022 12:09:19 -0400 X-Authentication-Warning: file01.intranet.prod.int.rdu2.redhat.com: mpatocka owned process doing -bs Date: Tue, 27 Sep 2022 12:09:19 -0400 (EDT) From: Mikulas Patocka X-X-Sender: mpatocka@file01.intranet.prod.int.rdu2.redhat.com To: Greg Kroah-Hartman cc: "Rafael J. Wysocki" , Christoph Lameter , Andrew Morton , Milan Broz , dm-devel@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] kernfs: fix a crash when two processes delete the same directory In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Sep 2022, Greg Kroah-Hartman wrote: > Can you see if 4abc99652812 ("kernfs: fix use-after-free in > __kernfs_remove") in linux-next fixes this for you or not? It seems to > be the same issue, as was also reported at: > https://lore.kernel.org/r/7f489b14-2fdc-3d91-c87e-6a802bd8592d@I-love.SAKURA.ne.jp > > thanks, > > greg k-h I'm running the test with the patch 4abc99652812 for 3 hours, no crash, so it's probably ok. Tested-by: Mikulas Patocka Mikulas