linux-kernel - Re: WinLink E850-96: WARNING: at block/blk-settings.c:204 blk_validate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Thu, 7 Mar 2024 09:32:31 -0800
From: Bart Van Assche <bvanassche@....org>
To: Christoph Hellwig <hch@....de>, Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: linux-block <linux-block@...r.kernel.org>, lkft-triage@...ts.linaro.org,
 open list <linux-kernel@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>,
 Christian Brauner <brauner@...nel.org>, Ulf Hansson
 <ulf.hansson@...aro.org>, Arnd Bergmann <arnd@...db.de>,
 Dan Carpenter <dan.carpenter@...aro.org>,
 Anders Roxell <anders.roxell@...aro.org>
Subject: Re: WinLink E850-96: WARNING: at block/blk-settings.c:204
 blk_validate_limits


On 2/29/24 06:21, Christoph Hellwig wrote:
> On Thu, Feb 29, 2024 at 07:44:01PM +0530, Naresh Kamboju wrote:
>> The arm64 WinLink E850-96 Board boot failed with 16K and 64K page size builds
>> Please find the below warning log on Linux next-20240229.
>> First noticed on the next-20240220 tag.
>>
>> This issue arises only when one of these Kconfig options is enabled.
>>    CONFIG_ARM64_16K_PAGES=y
>>    CONFIG_ARM64_64K_PAGES=y
> 
> That means this device doesn't set a max_segment_size, or one smaller
> than the page size.  This configurtio has never been supported by
> Linux (Bart has some patches to try to make it work), but with the
> new block limits API we now actively catch this and warn.

Hi Christoph,

Please let me know if you would like me to repost the patch series that
adds support to the block layer for DMA segments that are smaller than
the page size. Despite my requests to not support such hardware in the
Android kernel, that patch series ended up as an out-of-tree series
in the Android kernel and will continue to be maintained by the Android
core team for considerable time.

Thanks,

Bart.