From: Rob Landley <rob@landley.net>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Miaohe Lin <linmiaohe@huawei.com>
Cc: richard@nod.at, vigneshr@ti.com, David.Woodhouse@intel.com,
Artem.Bityutskiy@nokia.com, ext-adrian.hunter@nokia.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linfeilong@huawei.com
Subject: Re: [PATCH] mtd: fix size in mtd_info_user to support 64-bit
Date: Fri, 16 Jul 2021 08:34:45 -0500 [thread overview]
Message-ID: <f7f55c5e-f6b2-542c-66d2-20f4d88bf669@landley.net> (raw)
In-Reply-To: <20210716114808.246e92ba@xps13>
On 7/16/21 4:48 AM, Miquel Raynal wrote:
> Hi Miaohe,
>
> Miaohe Lin <linmiaohe@huawei.com> wrote on Fri, 16 Jul 2021 09:42:19
> +0800:
>
>> On 2021/7/16 7:02, Miquel Raynal wrote:
>> > Hi Miaohe,
>> >
>> > Miaohe Lin <linmiaohe@huawei.com> wrote on Thu, 8 Jul 2021 21:13:59
>> > +0800:
>> >
>> >> From: Feilong Lin <linfeilong@huawei.com>
>> >>
>> >> The size in struct mtd_info_user is 32-bit, which will cause errors
>> >> when obtaining the size of large-capacity MTD devices, such as TLC
>> >> NAND FLASH-2048Gb.
>> >
>> > Besides the fact that such devices are far from being supported by the
>> > Linux kernel, this change would basically break userspace, it cannot
>> > enter as-is...
>> >
>>
>> I see. Many thanks for your reply! We're working with these large-capacity
>> MTD devices now, any suggestion to work around this?
>
> The only way is to create a second UAPI.
Twelve years ago a patch was submitted to add a 64 bit MTD api:
https://lwn.net/Articles/326418/
But for some reason they only merged 64 bit erase:
https://github.com/torvalds/linux/commit/0dc54e9f33e2
But NOT the rest of the 64 bit mtd API in the same patch. I've never understood why.
Rob
next prev parent reply other threads:[~2021-07-16 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 13:13 [PATCH] mtd: fix size in mtd_info_user to support 64-bit Miaohe Lin
2021-07-15 23:02 ` Miquel Raynal
2021-07-16 1:42 ` Miaohe Lin
2021-07-16 9:48 ` Miquel Raynal
2021-07-16 13:34 ` Rob Landley [this message]
2021-07-17 1:55 ` Miaohe Lin
2021-07-22 8:47 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7f55c5e-f6b2-542c-66d2-20f4d88bf669@landley.net \
--to=rob@landley.net \
--cc=Artem.Bityutskiy@nokia.com \
--cc=David.Woodhouse@intel.com \
--cc=ext-adrian.hunter@nokia.com \
--cc=linfeilong@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).