From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: Relax user input size in pinmux_select()
Date: Tue, 13 Jun 2023 18:33:32 +0300 [thread overview]
Message-ID: <ZIiMTGaUNMKQCkfC@smile.fi.intel.com> (raw)
In-Reply-To: <24d8898b-1e3b-8180-e96b-a3296de178a9@web.de>
On Tue, Jun 13, 2023 at 04:38:17PM +0200, Markus Elfring wrote:
> > This is debugfs and there is no much sense to strict the user from
> > sending as much data as they can. The memdup_user_nul() will anyway
> > fail if there is not enough memory.
> >
> > Relax the user input size by removing an artificial limitaion.
>
> How are the chances to avoid typos also in such a change description?
Almost 0. This is now part of the non-rebased branch. It can be fixed
if and only if
- something really wrong happened before this patch in the tree and has
to be fixed, and
- maintainer will remember to fix the typo.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-13 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 13:12 [PATCH v1 1/2] pinctrl: Duplicate user memory in one go in pinmux_select() Andy Shevchenko
2023-06-04 13:12 ` [PATCH v1 2/2] pinctrl: Relax user input size " Andy Shevchenko
2023-06-09 7:22 ` Linus Walleij
[not found] ` <24d8898b-1e3b-8180-e96b-a3296de178a9@web.de>
2023-06-13 15:33 ` Andy Shevchenko [this message]
2023-06-13 18:17 ` [PATCH " Linus Walleij
2023-06-09 7:21 ` [PATCH v1 1/2] pinctrl: Duplicate user memory in one go " Linus Walleij
[not found] ` <39569326-6b1c-39b1-0eb2-f1c1d11251ec@web.de>
2023-06-13 15:35 ` [PATCH " Andy Shevchenko
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=ZIiMTGaUNMKQCkfC@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Markus.Elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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