From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (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 3A5AB3168EA; Tue, 3 Feb 2026 16:32:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770136363; cv=none; b=X5cY8OUSI2EiGYIER7uG2Vp99eMguId6gXB9e4pM2Huzbch+O7RuIGD117M9GbPoAXTJYkrcGSI8FSM4+m/YQlthXOgUeQsGHcuDZgoMAETKfWVcQAoYfqQD9Mfgz5DxvM0I8kd8sgiKpBbmwcH0OKciU2ty4cXu1KV6vOq+7BQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770136363; c=relaxed/simple; bh=7pZ++R7tg+0e49E+XZr/gIWurUNmxA2u9LbQhL0oOa0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=lmBIs5D7d0BMlXVysq3kHDs67e4Zx9nf2bPs8B5TgtfehwUIasf9CtvzKsxH/V/2Bxc+j+max8CoAABowq+2flvLtjqtNxWuliMufMtW/4KmfcwzdW3/bMUh61uLrRI1iC0pEIVgWdI2biAGprhd6nMZyDie1N3/79KGAjKd6ZQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 19FCF68BFE; Tue, 3 Feb 2026 17:32:37 +0100 (CET) Date: Tue, 3 Feb 2026 17:32:36 +0100 From: Christoph Hellwig To: Askar Safin Cc: dhowells@redhat.com, axboe@kernel.dk, brauner@kernel.org, cem@kernel.org, djwong@kernel.org, hch@lst.de, kundan.kumar@samsung.com, linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, viro@zeniv.linux.org.uk, willy@infradead.org, wqu@suse.com Subject: Re: [PATCH 03/14] iov_iter: extract a iov_iter_extract_bvecs helper from bio code Message-ID: <20260203163236.GA28989@lst.de> References: <1763225.1769180226@warthog.procyon.org.uk> <20260203102821.3017412-1-safinaskar@gmail.com> Precedence: bulk X-Mailing-List: linux-xfs@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: <20260203102821.3017412-1-safinaskar@gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) On Tue, Feb 03, 2026 at 01:28:21PM +0300, Askar Safin wrote: > David Howells : > > Can we make vmsplice() just copy data? > > vmsplice already caused at least one security issue in the past: > CVE-2020-29374 (see https://lwn.net/Articles/849638/ ). There may be other > CVEs, try to search CVE database. > > Also, I think vmsplice is rarely used. > > So, if you author a patch, which makes vmsplice equivalent to readv/writev, > and mention these CVEs, then, I think, such patch has high chance to > succeed. I'd be all for killing it, especially as getting it to properly pin the user buffers is still unsolved so far.