From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-01.1984.is (mail-01.1984.is [185.112.145.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D4E782C3259; Mon, 18 May 2026 14:33:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.112.145.69 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779114805; cv=none; b=LCS36DQX+KwfW7WX38k4LTslvlWCls3HrI8b/V5lO4ugegcEmFydrJ0m0PCR2QW9lW0iZNg/jXP27HCfudxLy+O2l3M5JsGK3JroUapuWFub+cRQltWN17aF164kik+1KARQEF+RyLLqfUzLaYL4I0kii+7bvF9Oq7wYvR9hJ6Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779114805; c=relaxed/simple; bh=6/3Bmy3SlFTGmZjZnqOGwGw9MTWGgv8VdupJ47MSV9c=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: Content-Type:MIME-Version; b=YN5euPohpUOrBGxXfH97T8XLW6aTATofR+nGRtVi6NgItjiRmPNMz1RuEnRSKafBir7dxB+1d/ZN+HJ37Zs94uUZb2g1cAUtryT8PxFTgATJ+/E6Bl6sAzIrH9y99L4tL5OoQWL2H9wk8hB20/7qeKu93qFZM9wZx3g7Yee5+uU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=berkoc.com; spf=pass smtp.mailfrom=berkoc.com; dkim=pass (2048-bit key) header.d=berkoc.com header.i=@berkoc.com header.b=icce/ZVo; dkim=temperror (0-bit key) header.d=berkoc.com header.i=@berkoc.com header.b=MuYzFaPs; arc=none smtp.client-ip=185.112.145.69 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=berkoc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=berkoc.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=berkoc.com header.i=@berkoc.com header.b="icce/ZVo"; dkim=temperror (0-bit key) header.d=berkoc.com header.i=@berkoc.com header.b="MuYzFaPs" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=berkoc.com; s=1984; h=MIME-Version:Content-Type:Message-ID:Date:References:In-Reply-To: Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=6/3Bmy3SlFTGmZjZnqOGwGw9MTWGgv8VdupJ47MSV9c=; b=icce/ZVoFWBC2E4Y7wvu+bS9qX CT2taSx3VhKrB9qASUgBO4Nid8aefXEpZdgZVjB5kTB9BQltIkg7JrP4f54UnQDYx6lYwR8yRo26G 8FjfKaWzoP/uQ/a2ncHsub+tlO5pnhblKW1Vivbaz/1aXI3xfzpUmSVCiwiAhk2BtUPcNPMX8PAfA V8UR+ZXICadH8bOGnT8dJ6DjwfUe2e0WwEZtEImNMz2irrwchiecVP2cvqvZ2QTocpTQb65tCwQjR stMI/LfF9HGhwQ1dNr2suzDupVbyCSal5J0egHQTrFDEReGwrG/fyO7kRbbfRP+99/5EyVc/zoRZ/ 6x3FI6IA==; Received: from localhost by mail-01.1984.is with utf8esmtp (Exim 4.96) (envelope-from ) id 1wOz1e-001hPX-1K; Mon, 18 May 2026 14:33:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berkoc.com; i=@berkoc.com; q=dns/txt; s=me; t=1779114770; h=message-id : date : subject : cc : to : from : sender : reply-to; bh=6/3Bmy3SlFTGmZjZnqOGwGw9MTWGgv8VdupJ47MSV9c=; b=MuYzFaPsoNCIUknTxqdQmQB/W3w0mJLCRVb7OF5tJpS01uRfMRvLtP1TKHBBnh9hLeM/V tcf++nqa+lpRqXNZqOXSF8vmm/y9udRWORdkRsDxhk6m7krNFbUuzuho8HDi8HoGZQHLY3d c9G8daMNkXco0aE/UvFhTxpKpY45XQ60O50ix/1kEbYgV+D2vCdu2pe/bgK66Er+pIUFRjb 2QKONW+aFxgqOLX+K9zNJoBsrM7bewQfxtwHcL5Sscs2vksPkLEqz2jJHha8uJ7XFvhDpqh 4/EkU1OknIYgo+9k7H/JddI6Jkwvq8uoO2KeBuIgDJgRRrL5jGBXJ3EtlSgA== From: Berkant Koc To: Bernd Schubert Cc: Greg KH , Miklos Szeredi , security@kernel.org, Joanne Koong , linux-kernel@vger.kernel.org, io-uring@vger.kernel.org, Jens Axboe , Pavel Begunkov , fuse-devel Subject: Re: [PATCH 2/2] fuse: wait for aborted connection before releasing last fuse_dev In-Reply-To: <2889c98c-21e8-47eb-903a-ea40bf5c8c04@ddn.com> References: <20260517-fuse-uaf-patch2@berkoc.com> <2889c98c-21e8-47eb-903a-ea40bf5c8c04@ddn.com> Date: Mon, 18 May 2026 16:32:18 +0200 Message-ID: <20260518143218.7c7c1689.clarification@berkoc.com> Content-Type: text/plain; charset=utf-8 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Spam-Score: -0.2 (/) X-Authenticated-User: me@berkoc.com X-Sender-Address: me@berkoc.com On Mon, 18 May 2026 11:47:00 +0000, Bernd Schubert wrote: > Would it be possible for you to test the attached patch? Reproducer and KASAN harness from the PATCH 2/2 series are staged. Two-arm plan: revert vs apply, race-widening debug hunk kept in both arms, 2x50 iterations each against torvalds/master tip, KASAN + lockdep + kmemleak enabled. Results back within the day once the base resolves. Blocker before I build. The patch references ring->chan and chan->conn. On mainline fs/fuse/dev_uring_i.h declares struct fuse_ring with struct fuse_conn *fc at line 110, no chan member; grep fuse_chan across fs/fuse/ returns zero hits. As-is the patch fails to compile with "struct fuse_ring has no member named chan". Is this based on a DDN topic branch that introduces a fuse_chan abstraction not yet upstream? If so, point me at the base tree or branch URL and I will rebase the test against that. If the references were meant to be ring->fc and fc against current mainline, confirm and I will adjust before the run. Assisted-by: Claude:claude-opus-4-7 berkoc-pipeline