From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <kees@kernel.org>, Carlos Maiolino <cem@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
linux-xfs@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v4 3/3] xfs: adjust handling of a few numerical mount options
Date: Wed, 21 Jan 2026 15:25:09 +0200 [thread overview]
Message-ID: <aXDTtenD9sRp3rUm@smile.fi.intel.com> (raw)
In-Reply-To: <db2897f9a625e7e9a6797fe32cc9364bde56d605.camel@yandex.ru>
On Wed, Jan 21, 2026 at 08:21:42AM +0300, Dmitry Antipov wrote:
> On Tue, 2026-01-20 at 14:55 -0800, Darrick J. Wong wrote:
>
> > Yes. Common code needs to have a rigorous self test suite, because I
> > see no point in replacing inadequately tested bespoke parsing code with
> > inadequately tested common parsing code.
>
> Nothing to disagree but:
>
> 1) My experience clearly shows that it takes a few patch submission
> iterations and a bunch of e-mails just to notice that the tests are
> mandatory for lib/ stuff. If it is really a requirement, it is worth
> to be mentioned somewhere under Documentation/process at least.
Feel free to submit an update! :-)
Sorry that I mentioned it one or two versions later than I should have.
> 2) I've traced memparse() back to 2006 at least, and (if I didn't miss
> something) there is no actual tests for it since them. And it's hard to
> see a point in testing memvalue() prior to testing its actual workhorse.
Yes, the historical code needs test cases. I added a few for get_option*()
for example before touching that code. So you're welcome to start test
cases for memparse(), I will appreciate that!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-21 13:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:52 [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse() Dmitry Antipov
2026-01-08 16:52 ` [PATCH v3 2/2] xfs: adjust handling of a few numerical mount options Dmitry Antipov
2026-01-08 17:06 ` [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse() Kees Cook
2026-01-08 17:42 ` Andrew Morton
2026-01-08 17:55 ` Kees Cook
2026-01-09 12:53 ` Carlos Maiolino
2026-01-08 20:05 ` Andy Shevchenko
2026-01-09 11:41 ` Dmitry Antipov
2026-01-09 17:09 ` Andy Shevchenko
2026-01-09 17:11 ` Andy Shevchenko
2026-01-11 0:01 ` Andrew Morton
2026-01-08 20:10 ` Andy Shevchenko
2026-01-09 11:05 ` Dmitry Antipov
2026-01-09 11:18 ` Andy Shevchenko
2026-01-20 0:06 ` Andrew Morton
2026-01-20 14:12 ` [PATCH v4 1/3] " Dmitry Antipov
2026-01-20 14:12 ` [PATCH v4 2/3] lib: fix a few comments to match kernel-doc -Wreturn style Dmitry Antipov
2026-01-20 14:47 ` Andy Shevchenko
2026-01-20 14:12 ` [PATCH v4 3/3] xfs: adjust handling of a few numerical mount options Dmitry Antipov
2026-01-20 14:59 ` Andy Shevchenko
2026-01-20 16:57 ` Dmitry Antipov
2026-01-20 21:49 ` Andy Shevchenko
2026-01-20 22:55 ` Darrick J. Wong
2026-01-21 5:21 ` Dmitry Antipov
2026-01-21 13:25 ` Andy Shevchenko [this message]
2026-01-20 14:45 ` [PATCH v4 1/3] lib: introduce simple error-checking wrapper for memparse() Andy Shevchenko
2026-01-20 14:46 ` 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=aXDTtenD9sRp3rUm@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=hch@infradead.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-xfs@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