From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (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 AE613239E75 for ; Mon, 9 Feb 2026 17:03:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770656633; cv=none; b=NFIcd279NQmkZkBRx+9c+P6MT7ljf1nki8zb0BCAqm5F5IVwdXQCxBEmWjZMAMpYJIt7CRew2PdduGLGA/6bPlLsr1pZeFlEjJEUxqeC198Z1eyxkMSuAAeU2LZ5jM1F0ex5aKalGkr4uWw+BHnA6RHCM0cUerW1k4wlZXJCKog= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770656633; c=relaxed/simple; bh=mQU+PSy3DUt4Ba5QB/r/C8tjmtjEIXHVIDDiAfHtCV8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ZXufao9JyI3r/3nx1NJJmp2G7ch2ZfRuEQ8TF808O9sw4e3hjJSs7foELiyCERoo/1ku6Snymqd4t2CZqH/AMxmxQqYz0hODP9lDwKtAVb3mE5se5HyuzomDioVMmAKet4RvzXLIYPTwiPHpFf0F1a3fw2D9w0ORkzEDO/mutDY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=l9GzceMS; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="l9GzceMS" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=yFYT5KAsSK/+i8yjAkGONo4LAjzIcnt+WlVcpAm32c4=; b=l9GzceMScI+HVZEVOYYinRjvh+ Z5tpUEfnVA+FQUVvP/nxBpkm6gALeEgR33ZW54EhOnp5SOSN4KgEh5xtYjfr+PDrlMH8V83FUNGb/ 43gMVg0iTodJXp8h3MO7BZSDKDf58lJ/5qLrreXmMNBSRzcrBOf21LH+4SFdPlvDxO7sDJFJilX37 I8Hx+zaIQgEU5UhLKEY+EaIcHrEBNz6rByGaAMg4Xdplv2LQqgZepkHHz7p4O3ZYzIunCEUwQHBXF t4UXFd5SRnluUg6jNJ/nC2e/lH3D+GMT01y8z6gW8Z1/UZt7irqK+O7hJTpI/MiePKwMdBwdsiGUa pZMLdIhA==; Received: from willy by casper.infradead.org with local (Exim 4.98.2 #2 (Red Hat Linux)) id 1vpUfs-00000009nTP-2BNW; Mon, 09 Feb 2026 17:03:48 +0000 Date: Mon, 9 Feb 2026 17:03:48 +0000 From: Matthew Wilcox To: oaygnahzz Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz Subject: Re: [PATCH] [QUESTION] ext4: Why does fsconfig allow repeated mounting? Message-ID: References: <20260209165944.12649-1-oaygnahzz@gmail.com> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260209165944.12649-1-oaygnahzz@gmail.com> On Tue, Feb 10, 2026 at 12:59:44AM +0800, oaygnahzz wrote: > Hi all, > The mount interface will report an error for repeated mounting, > but fsconfig seems to allow this. Why is that? The patch is incorrect and unrelated to the question > Thanks. > --- > fs/fsopen.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/fs/fsopen.c b/fs/fsopen.c > index 1aaf4cb2afb2..06a8711dd627 100644 > --- a/fs/fsopen.c > +++ b/fs/fsopen.c > @@ -300,6 +300,7 @@ static int vfs_fsconfig_locked(struct fs_context *fc, int cmd, > > /** > * sys_fsconfig - Set parameters and trigger actions on a context > + * > * @fd: The filesystem context to act upon > * @cmd: The action to take > * @_key: Where appropriate, the parameter key to set > -- > 2.33.0 > >