Re: [PATCH 5.10 24/40] f2fs: fix to seek incorrect data offset in inline data file

On 2020/12/24 15:52, Greg Kroah-Hartman wrote: On Thu, Dec 24, 2020 at 09:11:53AM +0800, Chao Yu wrote: Hi Greg, Thanks a lot for helping to resend and merge the patch. :) Not a problem, glad to help out. In the future, all you need to do is give us the git commit id that needs to be backpor

Re: [PATCH 5.10 24/40] f2fs: fix to seek incorrect data offset in inline data file

On Thu, Dec 24, 2020 at 09:11:53AM +0800, Chao Yu wrote: > Hi Greg, > > Thanks a lot for helping to resend and merge the patch. :) Not a problem, glad to help out. In the future, all you need to do is give us the git commit id that needs to be backported if it applies cleanly, no need to send th

Re: [PATCH 5.10 24/40] f2fs: fix to seek incorrect data offset in inline data file

Hi Greg, Thanks a lot for helping to resend and merge the patch. :) Thanks, On 2020/12/23 23:33, Greg Kroah-Hartman wrote: From: Chao Yu commit 7a6e59d719ef0ec9b3d765cba3ba98ee585cbde3 upstream. As kitestramuort reported: F2FS-fs (nvme0n1p4): access invalid blkaddr:1598541474 [ 25.725898

[PATCH 5.10 24/40] f2fs: fix to seek incorrect data offset in inline data file

From: Chao Yu commit 7a6e59d719ef0ec9b3d765cba3ba98ee585cbde3 upstream. As kitestramuort reported: F2FS-fs (nvme0n1p4): access invalid blkaddr:1598541474 [ 25.725898] [ cut here ] [ 25.725903] WARNING: CPU: 6 PID: 2018 at f2fs_is_valid_blkaddr+0x23a/0x250 [ 25.7259