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 D00D71F94F for ; Fri, 21 Aug 2026 01:31:26 +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=1787275887; cv=none; b=rxdSdaUpcGOGNUUcaL/H8lUBk9Xnw1B40yLDHIXTKEq7nD4hUnHj4wx5AkXR8261NvRCW8Qsa1eNcn/aAaVUChMfweol8YqLKE5GiHMHMzKDDA4fEOz6fkA5aVf3Z3mOW133b89RXM0TP5MHOcBrx+28k0O/fFQeSN0trwZW5wU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787275887; c=relaxed/simple; bh=wq3gTzfzTluAu+0h1jNK0VghPoUb5ayV2ZBJ6F8fJyU=; h=Message-ID:Date:MIME-Version:Cc:Subject:To:References:From: In-Reply-To:Content-Type; b=EWQs0pSfKVH2w6hpEBxgiFJSxCjFiLrDTM1PxxjefnuBx9nEnr6RPwWhaJj6D1VrOyil/lGrNmOa0Co42+lg707Ep151qJgTdcCf+xxAOnfSOqBigyOB0lcVfPSRSjAsK1VE1qNQvZMRkpRTY5p3f5FTFSbJJ7/UU6qRZMgtqo0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dPUP2Om4; 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="dPUP2Om4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6323C1F000E9; Fri, 21 Aug 2026 01:31:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787275886; bh=IY6G8JaoRbiuxH+olJlgFfR3MVeyH9MEMa+6auNiERI=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=dPUP2Om4SNO/ESPxV3AsD64bh97ig9fhECuI8KuvYCTusBshn7tDVarcSyW9jKLew Jqv3WvbVS5S3lDt/ITElUoGGTLuclTswut7uIsCdwHBhA/b3CuTgeBYA9uci2ldo4D /xN4d/9i024LQvXHETRTKOzdCii0L2wESZdD0kEJF4Y9PxF/vgD98SU2bOOUt5oCUa ELYEGBCo9LEsr2chgv3/0XjGoI/As1lyiXJ+P702/V+v5u/k/Onow71kLQZgW6EZHY Y+P9mp/XriNEbswvCwjsJWEQPauciZwXkAFNQFDtukqAbz7iIMlceFpHCWkEUVwxvV Z/a1+5rVOCRtA== Message-ID: <574ad500-a254-4430-925b-c1f8275d0a42@kernel.org> Date: Fri, 21 Aug 2026 09:31:23 +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 , stable@kernel.org Subject: Re: [f2fs-dev] [PATCH] f2fs: fix error handling on device alias check in rename and unlink To: Daeho Jeong , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com References: <20260821011812.2938998-1-daeho43@gmail.com> Content-Language: en-US From: Chao Yu In-Reply-To: <20260821011812.2938998-1-daeho43@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 8/21/26 09:18, Daeho Jeong wrote: > From: Daeho Jeong > > In f2fs_rename() and f2fs_unlink(), directly returning -EPERM when > encountering a device aliasing file bypasses the cleanup path. > > Fix this by setting err to -EPERM and jumping to the proper cleanup > labels (out_dir and out) instead of returning immediately. > > Fixes: a737e409a3d6 ("f2fs: support dynamic reserve/release for device aliasing") > Cc: stable@kernel.org > Signed-off-by: Daeho Jeong Reviewed-by: Chao Yu Thanks,