[LTP] LTP release preprations

[LTP] LTP release preprations

[Cyril Hrubis]

Hi!
It's about we start to prepare for the January release. We have roughly
a week for getting in all patches that should go in. So if there is
anything that should be reviewed please point it out ASAP.

As for me I'm going to (hopefully) finalize the ground rules patch and
send another version today.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Li Wang via ltp]

Cyril Hrubis <chrubis@suse.cz> wrote:

> It's about we start to prepare for the January release. We have roughly
> a week for getting in all patches that should go in. So if there is
> anything that should be reviewed please point it out ASAP.

I hope to promote the standardization of the LTP API namespace.
After some discussion, we still haven't found a satisfactory prefix.
e.g.

  tst_: core LTP API (lib/)
  etst_: non‑core extended library in (libs/)
  otst_: legacy/compat library (no new features)

But now, I'm also considering using tst_*, est_*, and ost_* directly.

That would great if we can finalize this before this release.

> As for me I'm going to (hopefully) finalize the ground rules patch and
> send another version today.

And, I will start the pre-release testing (against CentOS) soon.


--
Regards,
Li Wang


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Cyril Hrubis]

Hi!
>   tst_: core LTP API (lib/)
>   etst_: non‑core extended library in (libs/)
>   otst_: legacy/compat library (no new features)
> 
> But now, I'm also considering using tst_*, est_*, and ost_* directly.

Maybe tse_ (test extended) and tso_ (test old).

> That would great if we can finalize this before this release.

I do not have a strong opinion here, whatever is short enough would do.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Li Wang via ltp]

Hi Cyril,

tse_ and tso_ sound good. Short and distinct enough.
I will start to prepare my patch V2 based on this.

-- 
Regards,
Li Wang

On Thu, Jan 15, 2026 at 9:51 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
> Hi!
> >   tst_: core LTP API (lib/)
> >   etst_: non‑core extended library in (libs/)
> >   otst_: legacy/compat library (no new features)
> >
> > But now, I'm also considering using tst_*, est_*, and ost_* directly.
>
> Maybe tse_ (test extended) and tso_ (test old).
>
> > That would great if we can finalize this before this release.
>
> I do not have a strong opinion here, whatever is short enough would do.
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>


-- 
Regards,
Li Wang


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Petr Vorel]

Hi Cyril, all,

> Hi!
> It's about we start to prepare for the January release. We have roughly
> a week for getting in all patches that should go in. So if there is
> anything that should be reviewed please point it out ASAP.

> As for me I'm going to (hopefully) finalize the ground rules patch and
> send another version today.

I plan to merge today Martin's fix for lio_listio/2-1.c:
https://lore.kernel.org/ltp/20260115171847.28091-1-mdoucha@suse.cz/

I hope we could merge userfaultfd rewrite:
https://github.com/linux-test-project/ltp/pull/1280

Hopefully v7 "new cmd support option for needs_cmds" is ready now:
https://lore.kernel.org/ltp/20260109061716.20258-1-wegao@suse.com/

ioctl_pidfd02-06: Add CONFIG_USER_NS and CONFIG_PID_NS to needs_kconfigs
https://patchwork.ozlabs.org/project/ltp/patch/20251209211629.95436-1-terry.tritton@linaro.org/
(I somehow agree with Jan that sometimes just check /proc or /sys path is better
than imply kconfig, but majority agreed to use .needs_kconfigs).

Maybe fix clone10.c on 32 bit, if we find a root cause. This is just an
investigation:
https://lore.kernel.org/ltp/aWmqFAzdtsR0t5aJ@autotest-wegao.qe.prg2.suse.org/

We got no further response for some RPC fix, I'm not sure if it's ready:
https://lore.kernel.org/ltp/20260112015047.2184003-1-liujian56@huawei.com/

If we have time:
tst_filesystems01.c: Add test for .filesystems
https://patchwork.ozlabs.org/project/ltp/list/?series=481881&state=*

checkpatch.pl update
https://patchwork.ozlabs.org/project/ltp/list/?series=487179&state=*

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Jan Stancek via ltp]

On Fri, Jan 16, 2026 at 8:20 AM Petr Vorel <pvorel@suse.cz> wrote:
>
> Hi Cyril, all,
>
> > Hi!
> > It's about we start to prepare for the January release. We have roughly
> > a week for getting in all patches that should go in. So if there is
> > anything that should be reviewed please point it out ASAP.
>
> > As for me I'm going to (hopefully) finalize the ground rules patch and
> > send another version today.
>
> I plan to merge today Martin's fix for lio_listio/2-1.c:
> https://lore.kernel.org/ltp/20260115171847.28091-1-mdoucha@suse.cz/
>
> I hope we could merge userfaultfd rewrite:
> https://github.com/linux-test-project/ltp/pull/1280
>
> Hopefully v7 "new cmd support option for needs_cmds" is ready now:
> https://lore.kernel.org/ltp/20260109061716.20258-1-wegao@suse.com/
>
> ioctl_pidfd02-06: Add CONFIG_USER_NS and CONFIG_PID_NS to needs_kconfigs
> https://patchwork.ozlabs.org/project/ltp/patch/20251209211629.95436-1-terry.tritton@linaro.org/
> (I somehow agree with Jan that sometimes just check /proc or /sys path is better
> than imply kconfig, but majority agreed to use .needs_kconfigs).
>
> Maybe fix clone10.c on 32 bit, if we find a root cause. This is just an
> investigation:
> https://lore.kernel.org/ltp/aWmqFAzdtsR0t5aJ@autotest-wegao.qe.prg2.suse.org/

CLONE_SETTLS expects different parameters on x86 vs x86_64, I'd skip
32bit temporarily until it's resolved.

>
> We got no further response for some RPC fix, I'm not sure if it's ready:
> https://lore.kernel.org/ltp/20260112015047.2184003-1-liujian56@huawei.com/
>
> If we have time:
> tst_filesystems01.c: Add test for .filesystems
> https://patchwork.ozlabs.org/project/ltp/list/?series=481881&state=*
>
> checkpatch.pl update
> https://patchwork.ozlabs.org/project/ltp/list/?series=487179&state=*
>
> Kind regards,
> Petr
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Li Wang via ltp]

Hi All,

These two issues were discovered during pre-release testing
and should be resolved:

https://lists.linux.it/pipermail/ltp/2026-January/046231.html
https://lists.linux.it/pipermail/ltp/2026-January/046238.html

-- 
Regards,
Li Wang


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Andrea Cervesato via ltp]

Hi,

I still have file_attr05 pending
https://patchwork.ozlabs.org/project/ltp/patch/20251014-file_attr_eopnotsupp-v2-1-c9827c8d8127@suse.com/

It would be nice to merge it.

-- 
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Petr Vorel]

Hi,

I'd also like to get merged this old patchset:

v2 __builtin___clear_cache() => __clear_cache()
https://patchwork.ozlabs.org/project/ltp/list/?series=477319&state=*
https://lore.kernel.org/ltp/20251012194946.370905-1-petr.vorel@gmail.com/

I already got ack from Andrea, but since it's close to the release can somebody
else have look, please?

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Martin Doucha]

On 1/15/26 13:11, Cyril Hrubis wrote:
> Hi!
> It's about we start to prepare for the January release. We have roughly
> a week for getting in all patches that should go in. So if there is
> anything that should be reviewed please point it out ASAP.

Hello,
I'm finishing a partial revert of the ioctl_sg01 USB workaround which 
I'd like to get merged before release. I'll try to send the patch today.

-- 
Martin Doucha   mdoucha@suse.cz
SW Quality Engineer
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Andrea Cervesato via ltp]

Hi!

It would be nice to merge this one as well:

https://patchwork.ozlabs.org/project/ltp/list/?series=474077

-- 
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Cyril Hrubis]

Hi!
Are there any other fixes that should be considered before the git is
tagged?

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Petr Vorel]

> Hi!
> Are there any other fixes that should be considered before the git is
> tagged?

* ioctl_pidfd02-06: Add CONFIG_USER_NS and CONFIG_PID_NS to needs_kconfigs
https://patchwork.ozlabs.org/project/ltp/patch/20251209211629.95436-1-terry.tritton@linaro.org/
(Or I can prepare an alternative fix to do a runtime check, I also plan to send
a patch with formalising the rules)

* tst_net.sh fixes would be nice to get merged:
https://patchwork.ozlabs.org/project/ltp/list/?series=489902&state=*
https://lore.kernel.org/ltp/20260127131427.146592-1-pvorel@suse.cz/
https://lore.kernel.org/ltp/20260127131427.146592-2-pvorel@suse.cz/

https://patchwork.ozlabs.org/project/ltp/list/?series=489469&state=*

It should be safe to merge these:

* v5 tst_filesystems01.c: Add test for .filesystems
https://patchwork.ozlabs.org/project/ltp/list/?series=489469&state=*

* checkpatch.pl enhancement to check for typos
https://patchwork.ozlabs.org/project/ltp/list/?series=487179&state=*
(I did not merged it as I hoped for a discussion what else to enable for
warnings, but that could be done as a separate effort after the release).

FYI I dared to merge IMA fix:
https://github.com/linux-test-project/ltp/commit/1ba58805ea5466df5202ff2e7b5b3d0cd5c81c37

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Li Wang via ltp]

Petr Vorel <pvorel@suse.cz> wrote:

> * ioctl_pidfd02-06: Add CONFIG_USER_NS and CONFIG_PID_NS to needs_kconfigs
> https://patchwork.ozlabs.org/project/ltp/patch/20251209211629.95436-1-terry.tritton@linaro.org/
> (Or I can prepare an alternative fix to do a runtime check, I also plan to send
> a patch with formalising the rules)

The original patch should be safe to be merged.

Because we can disable or limit the creation of new namespaces only
by turning off the Kconfig options:

  - CONFIG_USER_NS
  - CONFIG_PID_NS

If those options are unset, the namespace type simply doesn’t exist
(no /proc/self/ns/user).

If they’re set, there isn’t a runtime knob (sysctl, proc, or sysfs) that can
disables them in general-purpose kernels.


-- 
Regards,
Li Wang


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Petr Vorel]

> Petr Vorel <pvorel@suse.cz> wrote:

> > * ioctl_pidfd02-06: Add CONFIG_USER_NS and CONFIG_PID_NS to needs_kconfigs
> > https://patchwork.ozlabs.org/project/ltp/patch/20251209211629.95436-1-terry.tritton@linaro.org/
> > (Or I can prepare an alternative fix to do a runtime check, I also plan to send
> > a patch with formalising the rules)

> The original patch should be safe to be merged.

> Because we can disable or limit the creation of new namespaces only
> by turning off the Kconfig options:

>   - CONFIG_USER_NS
>   - CONFIG_PID_NS

> If those options are unset, the namespace type simply doesn’t exist
> (no /proc/self/ns/user).

> If they’re set, there isn’t a runtime knob (sysctl, proc, or sysfs) that can
> disables them in general-purpose kernels.

Yeah, it's bool, let's merge it.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Li Wang via ltp]

Cyril Hrubis <chrubis@suse.cz> wrote:

Hi!
> Are there any other fixes that should be considered before the git is
> tagged?
>

No from my side, and LTP pre-release test looks good on our latest RHEL
9/10 series.

I think with the merge of some extra fixes suggested by Petr, we could
make it a release. Better on this Friday.

-- 
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Martin Doucha]

On 1/27/26 14:06, Cyril Hrubis wrote:
> Hi!
> Are there any other fixes that should be considered before the git is
> tagged?

Hi,
our pre-release testing has found a failure in userfaultfd03 on kernel 
v5.14 because the test can't find /dev/userfaultfd. According to kernel 
git, the file was added in this commit:

https://github.com/torvalds/linux/commit/2d5de004e009add27db76c5cdc9f1f7f7dc087e7

which was first merged into kernel v6.1. But the test has .min_kver="5.11".

Ricardo, how did you choose the minimal kernel version for this test?

I recommend removing the .min_kver attribute and checking for the 
presence of /dev/userfaultfd instead. If the file is missing and the 
kernel is older than v6.1, then TCONF, otherwise TBROK.

-- 
Martin Doucha   mdoucha@suse.cz
SW Quality Engineer
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Ricardo Branco]

On 1/28/26 11:52 AM, Martin Doucha wrote:
> On 1/27/26 14:06, Cyril Hrubis wrote:
>> Hi!
>> Are there any other fixes that should be considered before the git is
>> tagged?
>
> Hi,
> our pre-release testing has found a failure in userfaultfd03 on kernel 
> v5.14 because the test can't find /dev/userfaultfd. According to 
> kernel git, the file was added in this commit:
>
> https://github.com/torvalds/linux/commit/2d5de004e009add27db76c5cdc9f1f7f7dc087e7 
>
>
> which was first merged into kernel v6.1. But the test has 
> .min_kver="5.11".
>
> Ricardo, how did you choose the minimal kernel version for this test?

https://lwn.net/Articles/897260/

>
> I recommend removing the .min_kver attribute and checking for the 
> presence of /dev/userfaultfd instead. If the file is missing and the 
> kernel is older than v6.1, then TCONF, otherwise TBROK. 

Ok.  Will try to submit a fix ASAP.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Cyril Hrubis]

Hi!
> > I recommend removing the .min_kver attribute and checking for the 
> > presence of /dev/userfaultfd instead. If the file is missing and the 
> > kernel is older than v6.1, then TCONF, otherwise TBROK. 
> 
> Ok.  Will try to submit a fix ASAP.

Please do so till the end of today, so that we can include that in the
release.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Andrea Cervesato via ltp]

Hi!

On Thu Jan 15, 2026 at 1:11 PM CET, Cyril Hrubis wrote:
> Hi!
> It's about we start to prepare for the January release. We have roughly
> a week for getting in all patches that should go in. So if there is
> anything that should be reviewed please point it out ASAP.
>
> As for me I'm going to (hopefully) finalize the ground rules patch and
> send another version today.

There's one more thing to do and it's to push a new version of kirk a
minor fix. LTP should update it accordingly.

I didn't see any issue with kirk so far, so we should do this now before
the release, WDYT?

-- 
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] LTP release preprations

[Li Wang via ltp]

On Wed, Jan 28, 2026 at 5:13 PM Andrea Cervesato via ltp <ltp@lists.linux.it>
wrote:

> Hi!
>
> On Thu Jan 15, 2026 at 1:11 PM CET, Cyril Hrubis wrote:
> > Hi!
> > It's about we start to prepare for the January release. We have roughly
> > a week for getting in all patches that should go in. So if there is
> > anything that should be reviewed please point it out ASAP.
> >
> > As for me I'm going to (hopefully) finalize the ground rules patch and
> > send another version today.
>
> There's one more thing to do and it's to push a new version of kirk a
> minor fix. LTP should update it accordingly.
>

+1


> I didn't see any issue with kirk so far, so we should do this now before
> the release, WDYT?
>

Yes, better to have that v3.2.1 version together, thanks!

-- 
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp