[PATCH v3] fs: fat: Handle 'FAT sector size mismatch'

[Varadarajan Narayanan]

On Fri, Feb 13, 2026 at 08:39:07AM -0600, Tom Rini wrote:
> On Fri, Feb 13, 2026 at 11:19:27AM +0530, Varadarajan Narayanan wrote:
> > Balaji,
> >
> > > On 1/29/2026 2:11 AM, Tom Rini wrote:
> > > > On Thu, Jan 22, 2026 at 12:04:42PM +0530, Balaji Selvanathan wrote:
> > > >
> > > > > From: Varadarajan Narayanan <varadarajan.narayanan at oss.qualcomm.com>
> > > > >
> > > > > Do FAT read and write based on the device sector size
> > > > > instead of the size recorded in the FAT meta data.
> > > > >
> > > > > FAT code issues i/o in terms of the sector size. Convert that to
> > > > > device sector size before doing the actual i/o. Additionally,
> > > > > handle leading/trailing blocks when the meta data based block
> > > > > no and i/o size is not an exact multiple of the device sector
> > > > > size or vice versa.
> > > > >
> > > > > Tested on UFS device with sector size 4096 and meta data recorded
> > > > > sector size 512.
> > > > >
> > > > > Signed-off-by: Varadarajan Narayanan <varadarajan.narayanan at oss.qualcomm.com>
> > > > First thing, clang shows a lot of warnings from this:
> > > > https://source.denx.de/u-boot/u-boot/-/jobs/1365316
> > > > Second thing, filesystem tests do pass:
> > > > https://source.denx.de/u-boot/u-boot/-/jobs/1365314
> > > > Please make sure v4 is put through CI:
> > > > https://docs.u-boot.org/en/latest/develop/ci_testing.html
> > >
> > > Sure, will address the warnings and will put v4 through CI.
> >
> > Have posted v4. Please see [1].
> >
> > Tom,
> >
> > The CI failed while building am33xx kirkwood. When I locally reverted
> > the v4 change and tried to build amxx related platforms, I was getting
> > similar errors. It doesn't appear to be related to this change. I might
> > be wrong. Please let me know if that issue has to be resolved.
>
> This is presumably:
> https://dev.azure.com/u-boot/u-boot/_build/results?buildId=12821&view=logs&j=a007cd84-3be0-5a02-8a7a-a34fb3052485&t=216c79d4-eaff-5600-0b8f-3a63c01a45d6
>
> And yes, you need to fix that. Your changes lead to am335x_evm
> am335x_hs_evm am335x_hs_evm_spi failing to link due ot overflowing SRAM
> size.

Have posted v5 addressing this [1]. Please review.

Thanks
-Varada

1 - https://lore.kernel.org/u-boot/20260217035643.2383088-1-varadarajan.narayanan@oss.qualcomm.com/