From: Luis Chamberlain <mcgrof@kernel.org>
To: Joel Granados <j.granados@samsung.com>
Cc: linux-kselftest@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Remove child from struct ctl_table
Date: Sun, 18 Jun 2023 02:33:35 -0700 [thread overview]
Message-ID: <ZI7Pbw5WcJDDISYI@bombadil.infradead.org> (raw)
In-Reply-To: <20230616085922.3066990-1-j.granados@samsung.com>
On Fri, Jun 16, 2023 at 10:59:14AM +0200, Joel Granados wrote:
> This is part of the effort to remove the empty element of the ctl_table
> structures (used to calculate size) and replace it with an ARRAY_SIZE call. By
> replacing the child element in struct ctl_table with a flags element we make
> sure that there are no forward recursions on child nodes and therefore set
> ourselves up for just using an ARRAY_SIZE. We also added some self tests to
> make sure that we do not break anything.
>
> Patchset is separated in 4: parport fixes, selftests fixes, selftests additions and
> replacement of child element. Tested everything with sysctl self tests and everything
> seems "ok".
>
> 1. parport fixes: This is related to my previous series and it plugs a sysct
> table leak in the parport driver. @mcgrof: I'm just leaving this here so we
> don't have to retest the parport stuff
>
> 2. Selftests fixes: Remove the prefixed zeros when passing a awk field to the
> awk print command because it was causing $0009 to be interpreted as $0.
> Replaced continue with return in sysctl.sh(test_case) so the test actually
> gets skipped. The skip decision is now in sysctl.sh(skip_test).
>
> 3. Selftest additions: New test to confirm that unregister actually removes
> targets. New test to confirm that permanently empty targets are indeed
> created and that no other targets can be created "on top".
>
> 4. Replaced the child pointer in struct ctl_table with an enum which is used to
> differentiate between permanently empty targets and non-empty ones.
>
> V2: Replaced the u8 flag with an enumeration.
Thanks, I dropped the old patches and applied this new set. Pushed out
to sysctl-next.
Luis
next prev parent reply other threads:[~2023-06-18 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230616085926eucas1p10709e25a4c0246ed2b22da602f919b4e@eucas1p1.samsung.com>
2023-06-16 8:59 ` [PATCH v2 0/8] Remove child from struct ctl_table Joel Granados
[not found] ` <CGME20230616085927eucas1p265c6e3512e3102a7df507da9d3f1f094@eucas1p2.samsung.com>
2023-06-16 8:59 ` [PATCH v2 1/8] parport: plug a sysctl register leak Joel Granados
[not found] ` <CGME20230616085930eucas1p2d1b7ee012df532b3dcf15f96cd2f8c18@eucas1p2.samsung.com>
2023-06-16 8:59 ` [PATCH v2 2/8] test_sysctl: Fix test metadata getters Joel Granados
[not found] ` <CGME20230616085932eucas1p1d3d120da7944fc06d714035043697e4d@eucas1p1.samsung.com>
2023-06-16 8:59 ` [PATCH v2 3/8] test_sysctl: Group node sysctl test under one func Joel Granados
[not found] ` <CGME20230616085935eucas1p2439375978f0ee33afd6310a9f8c5d07a@eucas1p2.samsung.com>
2023-06-16 8:59 ` [PATCH v2 4/8] test_sysctl: Add an unregister sysctl test Joel Granados
[not found] ` <CGME20230616085937eucas1p2128b2ddb3c01c887a606f376de850767@eucas1p2.samsung.com>
2023-06-16 8:59 ` [PATCH v2 5/8] test_sysctl: Add an option to prevent test skip Joel Granados
[not found] ` <CGME20230616085939eucas1p24e5c916a261653ce64bb65c7d12d2830@eucas1p2.samsung.com>
2023-06-16 8:59 ` [PATCH v2 6/8] test_sysclt: Test for registering a mount point Joel Granados
[not found] ` <CGME20230616085941eucas1p152b54db1511bfdd1afab32621aec847e@eucas1p1.samsung.com>
2023-06-16 8:59 ` [PATCH v2 7/8] sysctl: Remove debugging dump_stack Joel Granados
[not found] ` <CGME20230616085944eucas1p14e8491c53f5390064035de1ffb354c7a@eucas1p1.samsung.com>
2023-06-16 8:59 ` [PATCH v2 8/8] sysctl: replace child with an enumeration Joel Granados
2023-06-18 9:33 ` Luis Chamberlain [this message]
2023-06-19 7:32 ` [PATCH v2 0/8] Remove child from struct ctl_table Joel Granados
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=ZI7Pbw5WcJDDISYI@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=j.granados@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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).