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 916FC3AA9D8 for ; Thu, 20 Aug 2026 23:58:27 +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=1787270308; cv=none; b=Zx7R1QL/f1mNe+Z9ivZj8i5BXpCl6g1sMnIXIjmSMNEU+5c/MZx3CCcbACUdYu/xZyX0/WtpBat+yer1Hm9l4OFmZPWdq9fKCgOajs8VaTtaZSlFXqcjPsbw2/RWvFA3fUwyClWTR9hOZjsXTmHtvCIGI5hGqejlz0ALt7qi8e4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787270308; c=relaxed/simple; bh=Fdkh9/Vp3U65ufEd98Cbk6e1U0yFu1grjkI3wnP9VCQ=; h=Message-ID:Date:MIME-Version:Cc:Subject:To:References:From: In-Reply-To:Content-Type; b=d2jk1i95Y2H3//lw74K1LfAWOB+WAubFN/ONmx1DXeepxiLmGuIf6ITufJr0EN8MozHTtsFnMYFfg6G8zGEd1IFe69qnPobDOBeCdUY+T0gzjX0bnMilCsXHBPl8Eywkc6bPwfqmB1x1yX/H7YM4vWMNeFEblj6VoMZ9BC6ufsY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=TCDvbQKt; 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="TCDvbQKt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 127851F00A3A; Thu, 20 Aug 2026 23:58:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787270307; bh=7Bcuvsj5+kPR+WToJ/zyp+G13hKZKfEiBz70wMjSQCA=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=TCDvbQKtwbbC85ws/mVMrXCCkrfYGDE9VHaDyjUIN0wXybjqZvx95ImZLFfpyilZY Mwg3sENECGRAliImndQ9peeM+4qVHf39dhMrACzFGJlahhPXsX46IvAWcZJohQ8ZpV hKh4K4xY5x1RQKkNUaZimZpU14M9Dyw2XHj0Uk419eVgNXla0QYaMC171QrgXKFd7o fKYCqIuD0GlOwPWUEryPhwilGM0Pl37d2BlS84y1Fwdy+U28afhPWRjB61ZR1ZO6ZU uBDfX65YFKT441QlioFuu9ryWYGD3q4jP3+kwRwoKznUY4p3apTX7RMNNPiSgBfrEM IjpgDL2+/LvzQ== Message-ID: Date: Fri, 21 Aug 2026 07:58:24 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: chao@kernel.org, Daeho Jeong Subject: Re: [PATCH v8] f2fs: support dynamic reserve/release for device aliasing To: Daeho Jeong , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com References: <20260820211641.1273552-1-daeho43@gmail.com> Content-Language: en-US From: Chao Yu In-Reply-To: <20260820211641.1273552-1-daeho43@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 8/21/26 05:16, Daeho Jeong wrote: > From: Daeho Jeong > > This patch adds a dynamic management feature to the existing device > aliasing functionality. It allows users to dynamically reserve or > release specific devices from the filesystem's free pool at runtime > through new ioctls. > > To support this, three new ioctls are introduced: > - F2FS_IOC_RESERVE_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. > > - F2FS_IOC_RELEASE_DEV_ALIAS: This releases the reserved space of a > previously reserved device aliasing file. It truncates the blocks > associated with the file, which makes them available for general > filesystem allocation again. > > - F2FS_IOC_GET_DEV_ALIAS_STATUS: This retrieves the current aliasing > status of a device aliasing file, returning whether the file is > released (inactive alias) or reserved (active alias, with blocks > fully allocated on the device). > > Signed-off-by: Daeho Jeong > Reviewed-by: Chao Yu > --- > v8: fixed device aliasing checks in f2fs_rename and f2fs_unlink. The fix looks good to me, let me skip to reply w/ RVB since the patch has already had it. Thanks,