From: David Laight <David.Laight@ACULAB.COM>
To: 'Artem Labazov' <123321artyom@gmail.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Namjae Jeon <namjae.jeon@samsung.com>,
Sungjong Seo <sj1557.seo@samsung.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] exfat: Avoid allocating upcase table using kcalloc()
Date: Tue, 24 Nov 2020 22:17:06 +0000 [thread overview]
Message-ID: <ebdf1f1769aa45cc8880155a4189f2a6@AcuMS.aculab.com> (raw)
In-Reply-To: <20201124194749.4041176-1-123321artyom@gmail.com>
From: Artem Labazov
> Sent: 24 November 2020 19:48
>
> The table for Unicode upcase conversion requires an order-5 allocation,
> which may fail on a highly-fragmented system:
ISTM that is the wrong way to do the case conversion.
It is also why having to do it is bloody stupid.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-11-24 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201124194858epcas1p49cacda6a9b4877ff125f25f4dc5fcadf@epcas1p4.samsung.com>
2020-11-24 19:47 ` [PATCH] exfat: Avoid allocating upcase table using kcalloc() Artem Labazov
2020-11-24 22:17 ` David Laight [this message]
2020-12-02 4:58 ` Sungjong Seo
2020-12-04 12:57 ` Artem Labazov
2020-12-07 6:23 ` Sungjong Seo
2020-12-07 9:34 ` [PATCH v3] " Artem Labazov
2020-12-08 2:22 ` Sungjong Seo
2020-12-04 13:33 ` [PATCH v2] " Artem Labazov
2020-12-07 4:32 ` Namjae Jeon
2020-11-24 18:50 [PATCH] " Artem Labazov
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=ebdf1f1769aa45cc8880155a4189f2a6@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=123321artyom@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.com \
--cc=stable@vger.kernel.org \
/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).