From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 B89291A2872 for ; Wed, 8 Jan 2025 06:27:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736317662; cv=none; b=bBf7pGGKh+qq2TG9G6T7KhxeoJalSEVhRIbEKc3rhxvA+yjF8aXJYsONUGVbQXRnSpSzIuXab8w2ARbMm9cNo45koHs8L7oNIw1Bb22kmWOkqtM/5Or+hX7wSCsWbz9a1pcXrQBT8TGb7Z8MEyNC3wkHYfw6AJXXK3jc7us5DfU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736317662; c=relaxed/simple; bh=a2yAQY2KOPfDKjwBNr/1FmjUUktElYewr4hbpJmgr5w=; h=Message-ID:Date:MIME-Version:Subject:To:References:Cc:From: In-Reply-To:Content-Type; b=nIhwClIGX6p18AxILrqkRPtiXozaeoDjHFarXBV6gZ9mUMbGxL/o2xDfCJsphFbnNM3Bpqv20k6BjdpPy5dK+bXoTZ/82H+VhgocgOWTJT+idckRuu1dWe95iGz40T5+LMAg8oTCGaA9o31EwN/7aqnTHorM8l22X0SK/+HR2Dk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=EOnchAc6; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="EOnchAc6" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7532AC4CED0; Wed, 8 Jan 2025 06:27:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1736317662; bh=a2yAQY2KOPfDKjwBNr/1FmjUUktElYewr4hbpJmgr5w=; h=Date:Subject:To:References:Cc:From:In-Reply-To:From; b=EOnchAc6x+zw0g7tLKmxdlHsVJYLqJkKlcVY3tMXWPVN2VQABAxk8AfuOcBsjqxMJ csdJ3AvLcjwX4kmdV+eSTCvqbMPPuWfObtwbX7COCzxxQRAm8Vd3l7Agmyv6Udycg8 H6f9hnYcELYHex99hPPIMwLNZK8BjP0cIfpVxJNCebJhgHDQmhFL5TDqsF82amDgUS L+8i1+iN63s0Nw+HsmT0z9NNRJMwwWQ9ZIvdu5Sd4RhZhDFWh38Z/fsTKuY1Mj7zX8 BrpEAXXK1cIDCsrDCntV5wm61+MPJDZedfPQLFMoOF7HMU/gFhUbG3mprDGqcLFMS1 1vgO+Lnv3jDuQ== Message-ID: <240d5a92-23a3-4494-8cb8-ac564a4782f5@kernel.org> Date: Wed, 8 Jan 2025 14:27:35 +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 Subject: Re: [f2fs-dev] [PATCH v2] f2fs: don't call block truncation for aliased file To: Jaegeuk Kim , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net References: <20250107023248.3702924-1-jaegeuk@kernel.org> Content-Language: en-US Cc: chao@kernel.org From: Chao Yu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2025/1/8 03:09, Jaegeuk Kim via Linux-f2fs-devel wrote: > This patch should avoid the below warning which does not corrupt the metadata > tho. > > [ 51.508120][ T253] F2FS-fs (dm-59): access invalid blkaddr:36 > [ 51.508156][ T253] __f2fs_is_valid_blkaddr+0x330/0x384 > [ 51.508162][ T253] f2fs_is_valid_blkaddr_raw+0x10/0x24 > [ 51.508163][ T253] f2fs_truncate_data_blocks_range+0x1ec/0x438 > [ 51.508177][ T253] f2fs_remove_inode_page+0x8c/0x148 > [ 51.508194][ T253] f2fs_evict_inode+0x230/0x76c > > Fixes: 128d333f0dff ("f2fs: introduce device aliasing file") > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,