[ANNOUNCE] Release and and v6.1.78-cip15

[ANNOUNCE] Release and and v6.1.78-cip15

[nobuhiro1.iwamatsu]

Hi,

CIP kernel team has released Linux kernel v6.1.78-cip15.
The linux-6.1.y-cip tree has been updated base version from v6.1.75 to v6.1.78.
And this release adds device versaclock3 fixes for Renesas ARM SoCs.

You can get this release via the git tree at:

  v6.1.78-cip15:
    repository:
      https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    branch:
      linux-6.1.y-cip
    commit hash:
      8e0cf035f64a98ea0d7ed2527a547f39866c37ba
    Fixed CVEs:
      CVE-2024-26581: netfilter: nft_set_rbtree: skip end interval element from gc
      CVE-2024-0340: vhost: use kzalloc() instead of kmalloc() followed by memset()
      CVE-2024-1086: netfilter: nf_tables: reject QUEUE/DROP verdict parameters
      CVE-2024-23849: net/rds: Fix UBSAN: array-index-out-of-bounds in rds_cmsg_recv
    added commits:
      CIP: Bump version suffix to -cip15 after merge from stable
      clk: versaclock3: Drop ret variable
      clk: versaclock3: Add missing space between ')' and '{'
      clk: versaclock3: Use u8 return type for get_parent() callback
      clk: versaclock3: Avoid unnecessary padding
      clk: versaclock3: Update vc3_get_div() to avoid divide by zero
      arm64: defconfig: Enable Renesas VersaClock 3 clock generator config

Best regards,
   Nobuhiro

RE: [ANNOUNCE] Release and and v6.1.78-cip15

[Chris Paterson]

Hello,

> From: nobuhiro1.iwamatsu@toshiba.co.jp
> <nobuhiro1.iwamatsu@toshiba.co.jp>
> Sent: Sunday, February 25, 2024 11:27 PM
> 
> Hi,
> 
> CIP kernel team has released Linux kernel v6.1.78-cip15.
> The linux-6.1.y-cip tree has been updated base version from v6.1.75 to
> v6.1.78.
> And this release adds device versaclock3 fixes for Renesas ARM SoCs.
> 
> You can get this release via the git tree at:
> 
>   v6.1.78-cip15:
>     repository:
>       https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git 
>     branch:
>       linux-6.1.y-cip
>     commit hash:
>       8e0cf035f64a98ea0d7ed2527a547f39866c37ba
>     Fixed CVEs:
>       CVE-2024-26581: netfilter: nft_set_rbtree: skip end interval element
> from gc
>       CVE-2024-0340: vhost: use kzalloc() instead of kmalloc() followed by
> memset()
>       CVE-2024-1086: netfilter: nf_tables: reject QUEUE/DROP verdict
> parameters
>       CVE-2024-23849: net/rds: Fix UBSAN: array-index-out-of-bounds in
> rds_cmsg_recv
>     added commits:
>       CIP: Bump version suffix to -cip15 after merge from stable
>       clk: versaclock3: Drop ret variable
>       clk: versaclock3: Add missing space between ')' and '{'
>       clk: versaclock3: Use u8 return type for get_parent() callback
>       clk: versaclock3: Avoid unnecessary padding
>       clk: versaclock3: Update vc3_get_div() to avoid divide by zero
>       arm64: defconfig: Enable Renesas VersaClock 3 clock generator config

Test results: 
- Dashboard: https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/
- Results comparison with previous release: https://squad.ciplatform.org/_/comparebuilds/?project=linux-cip/linux-6.1.y-cip&baseline=6.1.75-cip14_f555c0a7f&target=6.1.78-cip15_8e0cf035f&comparison_type=test
- Summary: No new regressions

Kind regards, Chris

> 
> Best regards,
>    Nobuhiro

Re: [ANNOUNCE] Release and and v6.1.78-cip15

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

Hi!

> Test results: 
> - Dashboard: https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/
> - Results comparison with previous release: https://squad.ciplatform.org/_/comparebuilds/?project=linux-cip/linux-6.1.y-cip&baseline=6.1.75-cip14_f555c0a7f&target=6.1.78-cip15_8e0cf035f&comparison_type=test
> - Summary: No new regressions

Ok, so I'm looking at squad to see if it is feasible to decode the
results.

I assume testing starts automatically at the push?

I see "Test jobs progress 31 / 31 (100%)", but the bar above it is
partly red. What does the red part mean?

It lists incomplete test jobs at
https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/testjobs/
. Is that expected? How should we deal with those?

Could we add big, green "This is okay to release" text somewhere, that
tells me that everything is okay without going through all the
details?

Thansk and best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: [ANNOUNCE] Release and and v6.1.78-cip15

[Chris Paterson]

[-- Attachment #1.1: Type: text/plain, Size: 3414 bytes --]

Hello Pavel,



> From: Pavel Machek <pavel@denx.de>

> Sent: Monday, February 26, 2024 12:05 PM

>

> Hi!

>

> > Test results:

> > - Dashboard: https://squad.ciplatform.org/linux-cip/linux-6.1.y-<https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/>

> cip/build/6.1.78-cip15_8e0cf035f/<https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/>

> > - Results comparison with previous release:

> https://squad.ciplatform.org/_/comparebuilds/?project=linux-cip/linux-<https://squad.ciplatform.org/_/comparebuilds/?project=linux-cip/linux-6.1.y-cip&baseline=6.1.75-cip14_f555c0a7f&target=6.1.78-cip15_8e0cf035f&comparison_type=test>

> 6.1.y-cip&baseline=6.1.75-cip14_f555c0a7f&target=6.1.78-<https://squad.ciplatform.org/_/comparebuilds/?project=linux-cip/linux-6.1.y-cip&baseline=6.1.75-cip14_f555c0a7f&target=6.1.78-cip15_8e0cf035f&comparison_type=test>

> cip15_8e0cf035f&comparison_type=test<https://squad.ciplatform.org/_/comparebuilds/?project=linux-cip/linux-6.1.y-cip&baseline=6.1.75-cip14_f555c0a7f&target=6.1.78-cip15_8e0cf035f&comparison_type=test>

> > - Summary: No new regressions

>

> Ok, so I'm looking at squad to see if it is feasible to decode the

> results.

>

> I assume testing starts automatically at the push?

>

> I see "Test jobs progress 31 / 31 (100%)", but the bar above it is

> partly red. What does the red part mean?



One of the LAVA jobs failed to complete.



>

> It lists incomplete test jobs at

> https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-<https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/testjobs/>

> cip15_8e0cf035f/testjobs/<https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/testjobs/>

> . Is that expected? How should we deal with those?



If the "incomplete" LAVA job has a green ticket next to it (as in this case), the job has already been resubmitted and successfully run again.

If there is a red cross, a LAVA job failed to complete and hasn't been resubmitted yet.

SQUAD admins (me & Sietze) can resubmit these LAVA jobs directly from SQUAD, then SQUAD automatically keeps track of it all.



>

> Could we add big, green "This is okay to release" text somewhere, that

> tells me that everything is okay without going through all the

> details?



There are two options.

1) You can look at the top level (https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/):

[cid:image001.png@01DA68AD.90D6AD30]

If in the circled section it is all green and “pass” – there are no issues.

If in the circled section there is a red “fail” bit, there have been builds or tests that have failed.



2) Look at an individual build (https://squad.ciplatform.org/linux-cip/linux-6.1.y-cip/build/6.1.78-cip15_8e0cf035f/)

If you scroll to the bottom there is a “Test results section”.

By default a “failures only” tick box is selected.

If there are any build or test failures then something will be shown here.

Or you can unselect the “failures only” tick box and you’ll get a view of all of the passed builds/tests as well:

[cid:image002.png@01DA68AD.E510B800]

Again, there will be red “fail” items here if there are issues.



Hopefully that clarifies things a bit.



Kind regards, Chris

[-- Attachment #1.2: Type: text/html, Size: 9304 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 23959 bytes --]

[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 26221 bytes --]

squad was Re: [ANNOUNCE] Release and and v6.1.78-cip15

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

Hi!

> > . Is that expected? How should we deal with those?
> 
> 
> 
> If the "incomplete" LAVA job has a green ticket next to it (as in this case), the job has already been resubmitted and successfully run again.
> 
> If there is a red cross, a LAVA job failed to complete and hasn't been resubmitted yet.
> 
> SQUAD admins (me & Sietze) can resubmit these LAVA jobs directly from SQUAD, then SQUAD automatically keeps track of it all.
>

Still looking at Squad. I submitted test merge to LAVA, and it is now
being tested at

https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-test

. Where can I find it in SQUAD?

And while browsing around, I stepped on this:

https://squad.ciplatform.org/linux-cip/

There is still lot of skips and fails there. The 5.10 ones are from 9
hours ago. What is going on there?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]