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 Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 473E1CD6E7C for ; Fri, 5 Jun 2026 22:10:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.sourceforge.net; s=beta; h=Content-Transfer-Encoding:Content-Type:Cc: Reply-To:From:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Subject:In-Reply-To:MIME-Version:References: Message-ID:To:Date:Sender:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=S6braq2Xoflw4pguGWAeuQ3HPctSCn6zM7Kp7w//doQ=; b=RdxYX0PCVdqLJoT5on551WY2w3 Rr2zE0sy1mOESx29SaMGfswW/k1YUI/jQT8uBN2HcQuk1MoT4yg/QGfhtybFhNSoRErnQptwqho9+ gnz3NLPT5BOdxcjaJg3FhdiVlxW1pJeqTIaKZkpJBMs38pYWXHMo/dG+Pi4m++p18+cE=; Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1wVckU-0006Ar-Fz; Fri, 05 Jun 2026 22:10:42 +0000 Received: from [172.30.29.66] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1wVckT-0006Af-1u for linux-f2fs-devel@lists.sourceforge.net; Fri, 05 Jun 2026 22:10:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; 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: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=iJT3Q7smY0LrmHruOEmo/PCSRB3GG8ERa4x6kmx4d+Y=; b=mmAWXI1VjGaNNPl6mHIgEhzXCh oFSULnEmkvoQzKn3yn7veNuSAYGP0LJWqdu0jCZhhwliNINQ5EBjqAXcnQ0KZQnC9VW0s4iCw6wjW 4UsjDDSZs5Z7GY5Jdt3LhM5fd8XFbP6+C24WeAWDGliCXRz4Ehru2wUo/R0bdci0ArMs=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; 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: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=iJT3Q7smY0LrmHruOEmo/PCSRB3GG8ERa4x6kmx4d+Y=; b=Z0n0EFaSIjgybD9A9LoT1/bFHX gG7VMgsetN6PB2VH2+MzPN0tx6SjuEUKHLIrEccmU4UOZE4wbdG9/SiswFtS+UOAPeZRDnZnWx7y0 K4bsZKJVEdoSQgnMA3YjDby7lKo+quGeJeIOd61W2aAy9LKlJSLBp0PlU4+qol4m/lJ4=; Received: from tor.source.kernel.org ([172.105.4.254]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1wVckS-00043C-3C for linux-f2fs-devel@lists.sourceforge.net; Fri, 05 Jun 2026 22:10:40 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id DC4DC600AE; Fri, 5 Jun 2026 22:10:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 622D31F00893; Fri, 5 Jun 2026 22:10:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780697429; bh=iJT3Q7smY0LrmHruOEmo/PCSRB3GG8ERa4x6kmx4d+Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=DZJs1NeGHa6Aj5cGd2/4LKJNYX2ZOA007sU5tt1nQypR4gNWPS3L9LOEZfYrAYKIQ RTq217bR6iiqBK2d7qIhYjnUT+KbWjx1CwcLmkqDXnchtgIfICxGsfaVqI1g/rHhjQ 3bQaKxcYxDY0FdR+r064rlpKMDClNrsBXkPzXQ8V8VlyvWXERTIOMaZjkeGUCd03CW /bvma0EHSo8m52mqnvJKuRkL8B8XbrisWxR1u/8GmeJ161Cy/OKrjM752FGbhY4Q4M AbLNTaNZSh4pqPSFWH6MO0rpf7I2xEyKdY0tVY66HSW6Gh5RlGEr1ik4a7CvL99VKN a9v2JnKDIS3gA== Date: Fri, 5 Jun 2026 22:10:27 +0000 To: Daeho Jeong Message-ID: <20260605221027.GA2312230@google.com> References: <20260605212504.1080138-1-daeho43@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20260605212504.1080138-1-daeho43@gmail.com> X-Headers-End: 1wVckS-00043C-3C Subject: Re: [f2fs-dev] [PATCH v2] f2fs: support dynamic include/exclude for device aliasing X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eric Biggers via Linux-f2fs-devel Reply-To: Eric Biggers Cc: Daeho Jeong , kernel-team@android.com, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On Fri, Jun 05, 2026 at 02:25:04PM -0700, Daeho Jeong wrote: > - F2FS_IOC_EXCLUDE_DEV_ALIAS: This reclaims the space occupied by a > device aliasing file. It first performs a capacity check, resets GC > victim information for the target range, marks the segments as in-use > to prevent new allocations, and then triggers GC to migrate existing > valid data out of the range. Finally, it reserves these blocks in the > SIT to effectively exclude the device from the usable capacity. Does this do anything to zeroize the device so that random data isn't leaked in it, or is that the responsibility of the userspace code that reallocates the device to something? > @@ -2214,7 +2231,8 @@ static const struct { > FS_INLINE_DATA_FL | \ > FS_NOCOW_FL | \ > FS_VERITY_FL | \ > - FS_CASEFOLD_FL) > + FS_CASEFOLD_FL | \ > + F2FS_DEVICE_ALIAS_FL) This is extending FS_IOC_GETFLAGS, which you probably don't really want to be doing, right? - Eric _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 E318D1FE47B for ; Fri, 5 Jun 2026 22:10:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780697430; cv=none; b=BF6fsgmkwWy/05ERXqQ7SQ3CCz/lz7wE3/aeFv9CoBxD48nQM8TTzZkRWLDoM5VePt7p2LsgYPxmIVnOarWlOsW1+MxDze2qI++ZhLbMQLSkSLPOQrOWzEQ3tugodiEaD/979jPRRBymEvktpXcOw44EUHyMmyMgRXAvJLJOHnk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780697430; c=relaxed/simple; bh=VmWY4wK3W6V0F7STjFDjEhBw28smu1H0r5IlJkzEYxM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=i+AtcC3TdIj+DkWGAAD/zr8Mn3xQ8NG3F+FJ5WycK1+kYK6XsJHQoig+9zfcWgfna9acsTrP2hQvzP4OBzATG5trmmtG94SCjwPUKan/aXDj/30BSAPKLjS7GBLLx9nATS+F9Ku/XSX3Ajtga+Yq4PuRK9P7wTc39XJXtlbYdJc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=DZJs1NeG; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="DZJs1NeG" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 622D31F00893; Fri, 5 Jun 2026 22:10:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780697429; bh=iJT3Q7smY0LrmHruOEmo/PCSRB3GG8ERa4x6kmx4d+Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=DZJs1NeGHa6Aj5cGd2/4LKJNYX2ZOA007sU5tt1nQypR4gNWPS3L9LOEZfYrAYKIQ RTq217bR6iiqBK2d7qIhYjnUT+KbWjx1CwcLmkqDXnchtgIfICxGsfaVqI1g/rHhjQ 3bQaKxcYxDY0FdR+r064rlpKMDClNrsBXkPzXQ8V8VlyvWXERTIOMaZjkeGUCd03CW /bvma0EHSo8m52mqnvJKuRkL8B8XbrisWxR1u/8GmeJ161Cy/OKrjM752FGbhY4Q4M AbLNTaNZSh4pqPSFWH6MO0rpf7I2xEyKdY0tVY66HSW6Gh5RlGEr1ik4a7CvL99VKN a9v2JnKDIS3gA== Date: Fri, 5 Jun 2026 22:10:27 +0000 From: Eric Biggers To: Daeho Jeong Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com, Daeho Jeong Subject: Re: [f2fs-dev] [PATCH v2] f2fs: support dynamic include/exclude for device aliasing Message-ID: <20260605221027.GA2312230@google.com> References: <20260605212504.1080138-1-daeho43@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@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: <20260605212504.1080138-1-daeho43@gmail.com> On Fri, Jun 05, 2026 at 02:25:04PM -0700, Daeho Jeong wrote: > - F2FS_IOC_EXCLUDE_DEV_ALIAS: This reclaims the space occupied by a > device aliasing file. It first performs a capacity check, resets GC > victim information for the target range, marks the segments as in-use > to prevent new allocations, and then triggers GC to migrate existing > valid data out of the range. Finally, it reserves these blocks in the > SIT to effectively exclude the device from the usable capacity. Does this do anything to zeroize the device so that random data isn't leaked in it, or is that the responsibility of the userspace code that reallocates the device to something? > @@ -2214,7 +2231,8 @@ static const struct { > FS_INLINE_DATA_FL | \ > FS_NOCOW_FL | \ > FS_VERITY_FL | \ > - FS_CASEFOLD_FL) > + FS_CASEFOLD_FL | \ > + F2FS_DEVICE_ALIAS_FL) This is extending FS_IOC_GETFLAGS, which you probably don't really want to be doing, right? - Eric