Debian Bug report logs - #1032104
linux: ppc64el iouring corrupted read

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Daniel Black <daniel@mariadb.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux: ppc64el iouring corrupted read

Date: Tue, 28 Feb 2023 03:13:18 +0000

Source: linux
Version: 5.10.0-21-powerpc64le
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: daniel@mariadb.org

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

From https://jira.mariadb.org/browse/MDEV-30728

MariaDB's mtr tests on a number of specific tests depend on the correct
kernel operation.

As observed in these tests, there is a ~1/5 chance the
encryption.innodb_encryption test will read zeros on the later part of
the 16k pages that InnoDB uses by default.

This affects MariaDB-10.6+ packages where there is a liburing in the
distribution.

This has been observed in the CI of Debian
(https://ci.debian.net/packages/m/mariadb/testing/ppc64el/)
and upstreams https://buildbot.mariadb.org/#/builders/318.
The one ppc64le worker that has the Debian 5.10.0-21 kernel,
the same as the Debian CI, has the prefix ppc64le-db-bbw1-*.

Test faults occur on all MariaDB 10.6+ builds in containers on this kernel.
There a no faults on non-ppc64le or RHEL7/8 based ppc64le kernels.

To reproduce:

apt-get install mariadb-test
cd /usr/share/mysql/mysql-test
./mtr --mysqld=--innodb-flush-method=fsync --mysqld=--innodb-use-native-aio=1 --vardir=/var/lib/mysql  --force encryption.innodb_encryption,innodb,undo0 --repeat=12 

A test will frequenty fail.

2023-02-28  1:41:01 0 [ERROR] InnoDB: Database page corruption on disk or a failed read of file './ibdata1' page [page id: space=0, page number=282]. You may have to recover from a backup.

(the page number isn't predictable)

The complete mtr error log of mariadb server is $PWD/var/log/mysqld.1.err

I tested on tmpfs. This is a different fault from bug #1020831 as:
* there is no iouring error, just a bunch of zeros where data was
  expected.
* this is ppc64le only.

Note, more serious faults exist on overlayfs (MDEV-28751) and remote
filesystems so sticking to local xfs, ext4, btrfs is recommended.

-- System Information:
Debian Release: bullseye
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Message #10 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Diederik de Haas <didi.debian@cknow.org>

To: Daniel Black <daniel@mariadb.org>

Cc: 1032104@bugs.debian.org

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Tue, 28 Feb 2023 07:24:14 +0100

[Message part 1 (text/plain, inline)]

On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> Source: linux
> Version: 5.10.0-21-powerpc64le
> Severity: grave
> Justification: causes non-serious data loss
> X-Debbugs-Cc: daniel@mariadb.org
> 
> >From https://jira.mariadb.org/browse/MDEV-30728
> 
> MariaDB's mtr tests on a number of specific tests depend on the correct
> kernel operation.
> 
> As observed in these tests, there is a ~1/5 chance the
> encryption.innodb_encryption test will read zeros on the later part of
> the 16k pages that InnoDB uses by default.
> 
> This affects MariaDB-10.6+ packages where there is a liburing in the
> distribution.
> 
> I tested on tmpfs. This is a different fault from bug #1020831 as:
> * there is no iouring error, just a bunch of zeros where data was
>   expected.
> * this is ppc64le only.

What was the last kernel where this problem did NOT occur?
It's probably needed to pinpoint the (upstream) commit that caused this error/
issue and the best start is normally finding the closest range with Debian 
kernel releases where it did not and did occur.

> -- System Information:
> Debian Release: bullseye
>   APT prefers jammy-updates
>   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500,
> 'jammy'), (100, 'jammy-backports') Architecture: ppc64el (ppc64le)
> 
> Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
> Init: unable to detect

Why is there no 'bullseye' in APT policy's output?
Mixing distrubutions (aka FrankenDebian) isn't recommended, but seeing no 
bullseye in there is odd, especially since the kernel version very much does 
look like Debian.

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Daniel Black <daniel@mariadb.org>

To: Diederik de Haas <didi.debian@cknow.org>

Cc: 1032104@bugs.debian.org

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Tue, 28 Feb 2023 18:45:08 +1100

On Tue, Feb 28, 2023 at 5:24 PM Diederik de Haas <didi.debian@cknow.org> wrote:
>
> On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> > Source: linux
> > Version: 5.10.0-21-powerpc64le
> > Severity: grave
> > Justification: causes non-serious data loss
> > X-Debbugs-Cc: daniel@mariadb.org
> >
> > >From https://jira.mariadb.org/browse/MDEV-30728
> >
> > MariaDB's mtr tests on a number of specific tests depend on the correct
> > kernel operation.
> >
> > As observed in these tests, there is a ~1/5 chance the
> > encryption.innodb_encryption test will read zeros on the later part of
> > the 16k pages that InnoDB uses by default.
> >
> > This affects MariaDB-10.6+ packages where there is a liburing in the
> > distribution.
> >
> > I tested on tmpfs. This is a different fault from bug #1020831 as:
> > * there is no iouring error, just a bunch of zeros where data was
> >   expected.
> > * this is ppc64le only.
>
> What was the last kernel where this problem did NOT occur?

2022-12-19 03:55:34 install linux-image-5.10.0-20-powerpc64le:ppc64el
<none> 5.10.158-2

no similar errors between ^ and ..

2023-01-24 03:19:59 install linux-image-5.10.0-21-powerpc64le:ppc64el
<none> 5.10.162-1
(no other linux image installs in between these two)

first failure found ~ Feb 4 2023. Unsure when kernel rebooted to this
kernel bug it does appear to be the last revision.
https://buildbot.mariadb.org/#/builders/318/builds/10008

log example https://ci.mariadb.org/32263/logs/ppc64le-debian-11/mysqld.1.err.7
(search for CURRENT_TEST: encryption.innodb_encryption) - contains hex
dump of page

> It's probably needed to pinpoint the (upstream) commit that caused this error/
> issue and the best start is normally finding the closest range with Debian
> kernel releases where it did not and did occur.
>
> > -- System Information:
> > Debian Release: bullseye
> >   APT prefers jammy-updates
> >   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500,
> > 'jammy'), (100, 'jammy-backports') Architecture: ppc64el (ppc64le)
> >
> > Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
> > Init: unable to detect
>
> Why is there no 'bullseye' in APT policy's output?
> Mixing distrubutions (aka FrankenDebian) isn't recommended, but seeing no
> bullseye in there is odd, especially since the kernel version very much does
> look like Debian.

Apologies for the FrankenDebian look. This was a jammy container and
jammy report bug with bullseye edited (badly) in the system info.

Message #20 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Daniel Black <daniel@mariadb.org>

To: 1032104@bugs.debian.org

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Mon, 6 Mar 2023 13:25:36 +1100

Since revering to linux-image-5.10.0-20 we've been free of the same errors.

Message #25 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Paul Gevers <elbrus@debian.org>

To: 1032104@bugs.debian.org, Daniel Black <daniel@mariadb.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Sat, 18 Mar 2023 18:16:18 +0100

[Message part 1 (text/plain, inline)]

On Mon, 6 Mar 2023 13:25:36 +1100 Daniel Black <daniel@mariadb.org> wrote:
> Since revering to linux-image-5.10.0-20 we've been free of the same errors.

On ci.debian.net I upgraded all ppc64el hosts to bookworm on 2023-03-09.

debian@ci-worker-ppc64el-04:~$ uname -a
Linux ci-worker-ppc64el-04 6.1.0-5-powerpc64le #1 SMP Debian 6.1.12-1 
(2023-02-15) ppc64le GNU/Linux

Can you check if the errors are still the same (yes, there's still 
intermittent failures).

Paul

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #34 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Otto Kekäläinen <otto@debian.org>

To: 1032104@bugs.debian.org, Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: linux: ppc64el iouring corrupted read

Date: Sat, 18 Mar 2023 23:19:29 -0700

Any updates on this one?

I am still seeing the main.index_merge_innodb failure in
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0
and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1679174850&raw=0.

Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian
5.10.162-1 (2023-01-21) ppc64el (ppc64le)

Message #39 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Otto Kekäläinen <otto@debian.org>, 1032104@bugs.debian.org

Cc: Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Sun, 19 Mar 2023 17:02:19 +0100

Hi,

On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> Any updates on this one?
> 
> I am still seeing the main.index_merge_innodb failure in
> https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0
> and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1679174850&raw=0.
> 
> Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian
> 5.10.162-1 (2023-01-21) ppc64el (ppc64le)

Remember that with the 5.10.162 upstream version the io_uring code was
rebased to the 5.15-stable one. So it is likely, and it maches the
verison ranges, that the regression was introduced with this
particular changes. Ideally someone with access to the given
architecture, can verify that the issue is gone with the current
5.10.175 upstream (where there were several followup fixes, in
particular e.g. a similar one for s390x), and if not, reports the
problem to upstream.

Paul Gevers asked if the issues are gone as well with 6.1.12-1
(or later 6.1.y series versions, which will land in bookworm). That
would be valuable information to know as well to exclude we do not
have the issue as well in bookworm.

Regards,
Salvatore

Message #44 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: 1032104@bugs.debian.org, Otto Kekäläinen <otto@debian.org>

Cc: Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Thu, 6 Apr 2023 22:02:24 +0200

Control: tags -1 + moreinfo

Hi
On Sun, Mar 19, 2023 at 05:02:19PM +0100, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> > Any updates on this one?
> > 
> > I am still seeing the main.index_merge_innodb failure in
> > https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0
> > and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1679174850&raw=0.
> > 
> > Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian
> > 5.10.162-1 (2023-01-21) ppc64el (ppc64le)
> 
> Remember that with the 5.10.162 upstream version the io_uring code was
> rebased to the 5.15-stable one. So it is likely, and it maches the
> verison ranges, that the regression was introduced with this
> particular changes. Ideally someone with access to the given
> architecture, can verify that the issue is gone with the current
> 5.10.175 upstream (where there were several followup fixes, in
> particular e.g. a similar one for s390x), and if not, reports the
> problem to upstream.
> 
> Paul Gevers asked if the issues are gone as well with 6.1.12-1
> (or later 6.1.y series versions, which will land in bookworm). That
> would be valuable information to know as well to exclude we do not
> have the issue as well in bookworm.

Were you able to verify this?

Regards,
Salvatore

Message #51 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Otto Kekäläinen <otto@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 1032104@bugs.debian.org, Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Sat, 8 Apr 2023 18:54:21 -0700

> > On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> > > Any updates on this one?
> > >
> > > I am still seeing the main.index_merge_innodb failure in
> > > https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0
> > > and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1679174850&raw=0.
> > >
> > > Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian
> > > 5.10.162-1 (2023-01-21) ppc64el (ppc64le)
> >
> > Remember that with the 5.10.162 upstream version the io_uring code was
> > rebased to the 5.15-stable one. So it is likely, and it maches the
> > verison ranges, that the regression was introduced with this
> > particular changes. Ideally someone with access to the given
> > architecture, can verify that the issue is gone with the current
> > 5.10.175 upstream (where there were several followup fixes, in
> > particular e.g. a similar one for s390x), and if not, reports the
> > problem to upstream.
> >
> > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > (or later 6.1.y series versions, which will land in bookworm). That
> > would be valuable information to know as well to exclude we do not
> > have the issue as well in bookworm.
>
> Were you able to verify this?

No, not yet.

I have not done new uploads to experimental after the one I mentioned
and linked above from March 18th.

The builds for unstable are passing because I forced the tests to run
with regular fsync instead of native I/O in
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/fc1358087b39ac6520420c7bbae2e536bc86748d.
I will test this again later but right now I don't want to do any
extra uploads as the package is pending unblock and inclusion in
Bullseye (Bug#1033811) and I don't want one single minor issue to
jeopardize getting fixes for multiple major issues forward.

Message #56 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Paul Gevers <elbrus@debian.org>

To: Otto Kekäläinen <otto@debian.org>

Cc: 1032104@bugs.debian.org

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Sun, 9 Apr 2023 21:23:18 +0200

[Message part 1 (text/plain, inline)]

Hi Otto,

On 09-04-2023 03:54, Otto Kekäläinen wrote:
>>> Paul Gevers asked if the issues are gone as well with 6.1.12-1
>>> (or later 6.1.y series versions, which will land in bookworm). That
>>> would be valuable information to know as well to exclude we do not
>>> have the issue as well in bookworm.
>>
>> Were you able to verify this?
> 
> No, not yet.
> 
> I have not done new uploads to experimental after the one I mentioned
> and linked above from March 18th.

I don't understand this point, so I wonder if you understood my 
question. Maybe you did, but in my view no new uploads are needed to 
answer the bookworm question.

> The builds for unstable are passing because I forced the tests to run
> with regular fsync instead of native I/O in
> https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/fc1358087b39ac6520420c7bbae2e536bc86748d.
> I will test this again later but right now I don't want to do any
> extra uploads as the package is pending unblock and inclusion in
> Bullseye (Bug#1033811) and I don't want one single minor issue to
> jeopardize getting fixes for multiple major issues forward.

My point was that I upgraded the ppc64el hosts where ci.debian.net runs 
the autopkgtests (so *not* the Debian build infrastructure). Since that 
upgrade, all tests on ci.debian.net *in every suite* have been using the 
bookworm (6.1.y) kernel.

E.g. in unstable MariaDb 1:10.11.2-1 (so before the "Prevent 
mariadb-test-run from using native I/O on ppc64el and s390x due to Linux 
kernel bug" change) passed on 2023-03-26 10:39 but failed on the same 
day at 14:40. Is any of the failures on ppc64el before 1:10.11.2-2 and 
after 2023-03-09 from the same kernel issue we're discussing here (and 
thus the kernel still needs fixing in bookworm). Or are all the failures 
in that time-span from something else, and thus can we conclude that the 
kernel *probably* (no proof of course) got fixed between the version of 
the kernel in bullseye and the version in bookworm.

Paul

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #61 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Otto Kekäläinen <otto@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 1032104@bugs.debian.org, Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Sun, 9 Apr 2023 15:30:35 -0700

[Message part 1 (text/plain, inline)]

> > > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > > (or later 6.1.y series versions, which will land in bookworm). That
> > > would be valuable information to know as well to exclude we do not
> > > have the issue as well in bookworm.
> >
> > Were you able to verify this?

Yes and new kernel did not fix it.

I reviewed now all ppc64el autopkgtest runs of src:mariadb at
https://ci.debian.net/packages/m/mariadb/testing/ppc64el/

This is still happening on latest kernel and latest src:mariadb in
bookworm. The failing test varies, but they all have in common that
they error on 'Database page corruption on disk'.

autopkgtest [20:11:55]: starting date and time: 2023-04-08 20:11:55+0000
autopkgtest [20:12:17]: testbed running kernel: Linux
6.1.0-7-powerpc64le #1 SMP Debian 6.1.20-1 (2023-03-19)
autopkgtest [20:12:39]: testing package mariadb version 1:10.11.2-1
Completed: Failed 6/1021 tests, 99.41% were successful.
Failing test(s): main.innodb_ext_key main.statistics_upgrade_not_done

Attached summary of downloading all recent logs and running:
$ zgrep -e 'starting date' -e 'running kernel' -e 'testing package
mariadb version' -e 'Completed: ' -e 'Failing test(s)' *.gz | tee
mariadb-autopkgtest-ppc64el-summary.txt

[mariadb-autopkgtest-ppc64el-summary.txt (text/plain, attachment)]

Message #66 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Otto Kekäläinen <otto@debian.org>, 1032104@bugs.debian.org

Cc: Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Thu, 25 May 2023 07:44:29 +0200

Hi Otto,

On Sun, Apr 09, 2023 at 03:30:35PM -0700, Otto Kekäläinen wrote:
> > > > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > > > (or later 6.1.y series versions, which will land in bookworm). That
> > > > would be valuable information to know as well to exclude we do not
> > > > have the issue as well in bookworm.
> > >
> > > Were you able to verify this?
> 
> Yes and new kernel did not fix it.
> 
> I reviewed now all ppc64el autopkgtest runs of src:mariadb at
> https://ci.debian.net/packages/m/mariadb/testing/ppc64el/
> 
> This is still happening on latest kernel and latest src:mariadb in
> bookworm. The failing test varies, but they all have in common that
> they error on 'Database page corruption on disk'.
> 
> autopkgtest [20:11:55]: starting date and time: 2023-04-08 20:11:55+0000
> autopkgtest [20:12:17]: testbed running kernel: Linux
> 6.1.0-7-powerpc64le #1 SMP Debian 6.1.20-1 (2023-03-19)
> autopkgtest [20:12:39]: testing package mariadb version 1:10.11.2-1
> Completed: Failed 6/1021 tests, 99.41% were successful.
> Failing test(s): main.innodb_ext_key main.statistics_upgrade_not_done
> 
> Attached summary of downloading all recent logs and running:
> $ zgrep -e 'starting date' -e 'running kernel' -e 'testing package
> mariadb version' -e 'Completed: ' -e 'Failing test(s)' *.gz | tee
> mariadb-autopkgtest-ppc64el-summary.txt

Are those issues still present with recent kernels? There were again
enough io_uring based changes which make worth rebase our checking on
those.

Regards,
Salvatore

Message #71 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Otto Kekäläinen <otto@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 1032104@bugs.debian.org, Diederik de Haas <didi.debian@cknow.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#1032104: linux: ppc64el iouring corrupted read

Date: Wed, 24 May 2023 23:30:48 -0700

Hello!

This is not fixed.

I sampled failing autopkgtests for MariaDB at
https://ci.debian.net/packages/m/mariadb/testing/ppc64el/ between May
7th and 22nd. They still have crashes that include error message
'Database page corruption on disk'. Both failing and passing ones were
running kernel: Linux 6.1.0-9-powerpc64le #1 SMP Debian 6.1.27-1
(2023-05-08) Most passing ones were on ci-worker-ppc64el-03, but also
on -02. The failing ones were on workers -01 and -02. Since -02 had
both failing and passing it indicates that this is not a hardware
issue.

The overall symptoms indicate that this is a software issue that
started on Feb 6th (kernel: Linux 5.10.0-21-powerpc64le) and it
happens sporadically, not on every run, and continues to happen.

- Otto

Message #76 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Timothy Pearson <tpearson@raptorengineering.com>

To: 1032104@bugs.debian.org

Subject: Still present in Bookworm

Date: Thu, 7 Sep 2023 23:10:27 -0500 (CDT)

We've started hitting this on a busy server after upgrading to Bookworm:

2023-09-07 17:00:31 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2023-09-07 17:00:31 0 [Note] Server socket created on IP: '127.0.0.1'.
2023-09-07 17:00:31 0 [Note] /usr/sbin/mariadbd: ready for connections.
Version: '10.11.3-MariaDB-1'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 12
2023-09-07 17:00:31 0 [Note] InnoDB: Buffer pool(s) load completed at 230907 17:00:31
2023-09-07 20:35:06 8630 [ERROR] InnoDB: Database page corruption on disk or a failed read of file './database/data_table.ibd' page [page id: space=393, page number=1534]. You may have to recover from a backup.
2023-09-07 20:35:06 8630 [Note] InnoDB: Page dump (8192 bytes):
2023-09-07 20:35:06 8630 [Note] InnoDB: 86c518ee000005fe000005fd000005ff000000067ee5a53145bf000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 000000000189000f3eff803d000000003e030002003a003b0000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000045a00000000000000000000000000000000000000006881
2023-09-07 20:35:06 8630 [Note] InnoDB: 12d4ae6314accb64e0a86304000000ffffb55a4b8f6557796d5eb10dee577503
2023-09-07 20:35:06 8630 [Note] InnoDB: c64ee090070c90e9fd7e2014256e140c31c2b84d193051d88fefebbe72b9caaa
2023-09-07 20:35:06 8630 [Note] InnoDB: aa36b4985494699461a42852fe41a48ca248f91b5186496a1009f10320bc42d6
2023-09-07 20:35:06 8630 [Note] InnoDB: bef79c7b6fd53d7546a73df0b5caf5d53d6b7dafb5f63ed7ba3bdddbd7ceaeb5
2023-09-07 20:35:06 8630 [Note] InnoDB: 7fbefdb3d5e7b58ff2e2804eeedd3fa674ba789fee9547e9f8f4e4deebc7f4ee
2023-09-07 20:35:06 8630 [Note] InnoDB: e2f1bb2fef53393d3a7ef96be5e8f0e5d716f9381d3fb9f7069da6c5c1f26727
2023-09-07 20:35:06 8630 [Note] InnoDB: f71eec7ff5de57d2f13bf71e3c3a7aefbdc5e1c3ee95f4b013f28b27ef3f54c6
2023-09-07 20:35:06 8630 [Note] InnoDB: a44aac65a0646a544255978c7554b3d05652ff28ff3d12da3fdd5efff9cceaf3
2023-09-07 20:35:06 8630 [Note] InnoDB: f9bf6a9f7ff9853ffef2f667ff3bd7b2d4e43c9134ae70a69088490b1b6d0a2a
2023-09-07 20:35:06 8630 [Note] InnoDB: 7852f8bd97ae751feb1e0c1cfc7c6e0ebe4e3fa483e3270d8074ce09a77dd245
2023-09-07 20:35:06 8630 [Note] InnoDB: 7b321c284b67524ec12525580ed8b742c631dfbc3f85d9daa0133952d6280ab5
2023-09-07 20:35:06 8630 [Note] InnoDB: b028926a9456a6500d8b15e6dbdd7707ccfffbd4f27e1f7fa0c1705e0ac79c95
2023-09-07 20:35:06 8630 [Note] InnoDB: cb1c44c93269ca8695676d4b60dec9fa10388efff6fff4b8bfb4fd39e0a72cbc
2023-09-07 20:35:06 8630 [Note] InnoDB: 2c26daacaab2c20a5d3c809baa6355a29415feadbaffc5dcf8df4a070774daa5
2023-09-07 20:35:06 8630 [Note] InnoDB: c3da80d40684a565112db9a26a55896ba254bda7ec8a14b6e4818191d0710eae
2023-09-07 20:35:06 8630 [Note] InnoDB: ffd31407316a8a3a3b67854825e69482cd5278958b032f3d077bddf7060e7e39
2023-09-07 20:35:06 8630 [Note] InnoDB: 3707f7d3c9a3ee0de2c7402254c39102f08aaa751445db2475cd35e8685cd241
2023-09-07 20:35:06 8630 [Note] InnoDB: ca5a060a7623c719f8d4c15417184e5c925146061b0c33eace07e3654ac58283
2023-09-07 20:35:06 8630 [Note] InnoDB: 9e81e7bb3707067e357f172c96c5bc4c3fb28c311738666b63b5a1c860220aa0
2023-09-07 20:35:06 8630 [Note] InnoDB: ea628c8f9b06d8c48ca3defbd054de0ba98c660bd12a7c93641f3102285b6f63
2023-09-07 20:35:06 8630 [Note] InnoDB: 492a8715ea9bdd5b03ea5fcf8e3a1d1086f6c93bb46ce0200b5b4c7b2f7d724e
2023-09-07 20:35:06 8630 [Note] InnoDB: 3b5652b28dca5a5b83e5b0067e316c1cfbcdff9cca78100163d44aad35a66921
2023-09-07 20:35:06 8630 [Note] InnoDB: 937c44fb57a525c7487685fd56f79d01fb6fe6c6fe95633a39e9904384371482
2023-09-07 20:35:06 8630 [Note] InnoDB: 6b4e967c102a455d6d515a4b9b4375687965fd00fe72dc38fadb7f3f95791fdb
2023-09-07 20:35:06 8630 [Note] InnoDB: 2a11ca05cc561d42162260b21699bc9414d3d9e54df77f73a37f351d3ea4e325
2023-09-07 20:35:06 8630 [Note] InnoDB: 8050b35656b1e06c6370b93a8995a46b72a8f694f3007c2b641cf38dbda98cd7
2023-09-07 20:35:06 8630 [Note] InnoDB: a48553598548c280670cba5c94773561b4b0952bcccf76af0f987ffb34aa7db9
2023-09-07 20:35:06 8630 [Note] InnoDB: da83ab46d59443abbb1c83748c1fa4429cbc4a7abbcc2726da07a6d092d1de60
2023-09-07 20:35:06 8630 [Note] InnoDB: 60586da9266b52a02a5bad83578c939dbdb63f44ce57df8b9372f4f8f0b47bb3
2023-09-07 20:35:06 8630 [Note] InnoDB: 89b2e5682e3a20d55201371592229a9a527602722e665a36ddaac47743c739d8
2023-09-07 20:35:06 8630 [Note] InnoDB: fbc7290ed890434547634df499547186a3935240d529cb7dc637da66ff037373
2023-09-07 20:35:06 8630 [Note] InnoDB: d06fa7878b93533a6e304cb04a64af183c44e858283cfcc0d79065117993fa9d
2023-09-07 20:35:06 8630 [Note] InnoDB: c071fc2ffc5d8f7bb4cb33a5040e72c56c0f6d7114c8298af83236d5bb7ebedf
2023-09-07 20:35:06 8630 [Note] InnoDB: e886dcef7f706efc5f5df069f7e034adbad689e8bc434f1379a36cc88692a4a2
2023-09-07 20:35:06 8630 [Note] InnoDB: 30dcbca8d10de02f468d237ff1afa7328f0de25451b10a7210b34d356b2f8268
2023-09-07 20:35:06 8630 [Note] InnoDB: d97769691c2e56ff879e6ef52f2d092bacf0a86a4c55845ca3774a90909804d9
2023-09-07 20:35:06 8630 [Note] InnoDB: 5be9cd78f54fb899bbff35957dd02c39596ea34ee2bb4a30824a292e65d326c2
2023-09-07 20:35:06 8630 [Note] InnoDB: 8a83ebddb7070e3efc54b23f8873ebd0e559c0c5b0868c4d86741216cf22bd76
2023-09-07 20:35:06 8630 [Note] InnoDB: 4aae77fb85a071dc9ffcda54ee8d0b64858456924ddc84c432162a51156904fb
2023-09-07 20:35:06 8630 [Note] InnoDB: ba93fb8fcc8dfb1b47197fa91bfcc972f2a994c8d60c0ab4d3c55ad80c9231c3
2023-09-07 20:35:06 8630 [Note] InnoDB: db5586de1ad08f848e73b0f72f531c484c5a4f5c811cfed1674ea4d84348c052
2023-09-07 20:35:06 8630 [Note] InnoDB: 8464dd8a8367ba6f0e1cfccedc1cbc72f4a3f6f0144a0140c732a0d29d28d8f0
2023-09-07 20:35:06 8630 [Note] InnoDB: c5482278793279ede5fa5f1fc73aed60a1da31df484ad846efb585810fd926f2
2023-09-07 20:35:06 8630 [Note] InnoDB: 156bbe0c2a76a3e4f69f991bebba617b143ebb484a09176bc123314c548da87a
2023-09-07 20:35:06 8630 [Note] InnoDB: e89912a0ac07d097e3c6d15fff8729f445085fb4b099633136628e0886be112a
2023-09-07 20:35:06 8630 [Note] InnoDB: 570502d4d9250dbfffecdce8ffb4d6eef468ddb2ca151f858ccdb32b2e8c1927
2023-09-07 20:35:06 8630 [Note] InnoDB: 35a6ae13860c723e80bf14368efdce3ff79847279c8b1cb1483c0689488aa34a
2023-09-07 20:35:06 8630 [Note] InnoDB: b23a1b63e5aad1547d956f75fa737363bf7ff4f8bda3c3eefec1c688e9424934
2023-09-07 20:35:06 8630 [Note] InnoDB: 7d2d12e510481a56311a2ddb11035a7fc03f123acec1dd5f4e714031cb182a4c
2023-09-07 20:35:06 8630 [Note] InnoDB: aa66d855d84538998456a7522d74c64ef57f746e0edea2dc0d95bc9438ca6102
2023-09-07 20:35:06 8630 [Note] InnoDB: 63afbbaa0d7c5cca521be94a33eed87ceb43bbcb71e3e83ff3e753e80bdaddc3
2023-09-07 20:35:06 8630 [Note] InnoDB: 3360ac94e69703042ecc5332251743deafd03fd77d6b40ffb1b9d1b775b57231
2023-09-07 20:35:06 8630 [Note] InnoDB: b01390953e850cff622a2b46dbe3bf418181a11d60af03aea8f8b7a7f04aecb2
2023-09-07 20:35:06 8630 [Note] InnoDB: e0618ebc45d75b069f9c1c36bc232c3cd1cfba2d45fbfcec157fb0204cac37e8
2023-09-07 20:35:06 8630 [Note] InnoDB: fd05fd7079509359581730dba340827db0d2e91a241b4613bab4aef7cb81e3f8
2023-09-07 20:35:06 8630 [Note] InnoDB: 5ffa418f7b74daf95c8db3328b82d5e6e1965595980255a8a20d8b1ddfba7f7d
2023-09-07 20:35:06 8630 [Note] InnoDB: 6efc6fc0b82cde5b153aa5a0929232a00245a6104c088e9314b56010ad0b7d2b
2023-09-07 20:35:06 8630 [Note] InnoDB: 641cf30bff368539540beb2a216185363198a29820245502e7c5547576b9c36f
2023-09-07 20:35:06 8630 [Note] InnoDB: cc8d791025b0a3cbcab546a3ad0bb6b90a4e79596d115ae7681dd976743800bf
2023-09-07 20:35:06 8630 [Note] InnoDB: 1c7745c5bf3a85beb513d0c3256ab8a500a98ca5264d74ec984be9e7dbe66c72
2023-09-07 20:35:06 8630 [Note] InnoDB: ffe6ec15bf7dc2b812f25c19e30ddb0cd9878df709eb3ec154e78241a4d73676
2023-09-07 20:35:06 8630 [Note] InnoDB: 37729c8117e314034db353b414b1550a2c037b5335c8208a0a633e9e5deef95b
2023-09-07 20:35:06 8630 [Note] InnoDB: 7333b06d489689cc3915817463ce5a0b856360abb0e1132c07265d5d17c04ee0
2023-09-07 20:35:06 8630 [Note] InnoDB: 38fe1b931baea45a32495555b0c95ba66c03050b3a82105aee56c0edd9f1d301
2023-09-07 20:35:06 8630 [Note] InnoDB: e28f9f746f1e3f2eef2c159ec36a631d0a716c87f506dde8329e0f8951717340
2023-09-07 20:35:06 8630 [Note] InnoDB: bf1b7905035f9faa000fd9c4d942e7b8101304553432b559ab72c8c5f767955b
2023-09-07 20:35:06 8630 [Note] InnoDB: 3e7ef8ebf3a9f9c74fba571e9f9e1e1d2e4f2ab3f7ed7a8a63ab013c8383af31
2023-09-07 20:35:06 8630 [Note] InnoDB: c498c401d2736de52e468d23bffdb753c89d09c4f08cec0b5885978bf0325e54
2023-09-07 20:35:06 8630 [Note] InnoDB: 671c17277715de9db9915fb8623979b41c7fc54587d5ae29b69ce359a03e8286
2023-09-07 20:35:06 8630 [Note] InnoDB: bbb39cb55e2bdc91d0710eae3f3b997d83af826d8c5ab7bb40b051bc31c61732
2023-09-07 20:35:06 8630 [Note] InnoDB: a6c2d09df5fdbfaeffbb3372f0dae2e1a3d3cd0018d47a32ca7a11d81a57a5ce
2023-09-07 20:35:06 8630 [Note] InnoDB: 8ae033abc174c2f338d4404fc1f94ee03801777b8bf3e59f6c7f0e04c03f423d
2023-09-07 20:35:06 8630 [Note] InnoDB: bb0c5551500012822f5412299ba423e7f5e5ccfa20e3e3b313d06e5adea5954e
2023-09-07 20:35:06 8630 [Note] InnoDB: 15112b9e2a9a115d296a460e2443d95ba95c3bad1fb06fc75c51fbff3a055bd9
2023-09-07 20:35:06 8630 [Note] InnoDB: a00dc49dd4a129c88412306ca369175402993febb5ce7027b5ff89d961df3f38
2023-09-07 20:35:06 8630 [Note] InnoDB: 3a7db4dadd04d050f2a16da1764bc2962341e734eda5ab1eaea3cfb742c641df
2023-09-07 20:35:06 8630 [Note] InnoDB: bc3b091afad1e8666572038d6d0a0b45c256d61612633dead676f693f3e7ba5d
2023-09-07 20:35:06 8630 [Note] InnoDB: 2e3d583c3c5cad3a6dad97b2fac439266fc0023bc102ea3324d8cc75b62f445d
2023-09-07 20:35:06 8630 [Note] InnoDB: 91ef3f99820e07a35c52edb633b091466a6cd252a986d0d64d0ffd6ef71703f4
2023-09-07 20:35:06 8630 [Note] InnoDB: 176687be69d74d1695b382480237254ed145ed15c63f2bb42436d1a072cfc762
2023-09-07 20:35:06 8630 [Note] InnoDB: afa880d7a668284557b225fa7601042f5149a2c89493e44bcea11f77b73672e7
2023-09-07 20:35:06 8630 [Note] InnoDB: 53f3977d3aaeddebe9c9d0bdda60b911fc6b942eab220be5a414267eb0ecf1e3
2023-09-07 20:35:06 8630 [Note] InnoDB: 75ed5f8a1b87bff7e329f83a57f8e4223c5bfcfd185d2d5a2b6983a7948beadf
2023-09-07 20:35:06 8630 [Note] InnoDB: c7b8d37d7f80ffe2d3ab82cd0d6b0c5665c945381242962420c14906e74329ae
2023-09-07 20:35:06 8630 [Note] InnoDB: b841f19e8f848e9370fd5b3df89f6e7f0e2440505595c9aa2aa0f89408d69317
2023-09-07 20:35:06 8630 [Note] InnoDB: 2ae59ca9ba68766ae0a5a75003d0ee5bb934317390780c8e45e4a0544e8c2d00
2023-09-07 20:35:06 8630 [Note] InnoDB: 236a35e4afd8d4c0c5b82b6ae0c393358091ef4596d2434fc056dbc8107f2e4a
2023-09-07 20:35:06 8630 [Note] InnoDB: 618531b19f045b1bff776787df5bb7d5ff5d568023f8f994828f2881927d3122
2023-09-07 20:35:06 8630 [Note] InnoDB: 1aa85e1533f6821af0ef045e41c0ad29020c646eb20ed8b90d81a2bc90026eab
2023-09-07 20:35:06 8630 [Note] InnoDB: 42664078f536ffd9cdb1ceefcd4e403ba6698f5f317b8c859d0f50a170f64449
2023-09-07 20:35:06 8630 [Note] InnoDB: c2fa69114c9676ad75cf87df1f87fbfcab537059133c64661605cabe2a995546
2023-09-07 20:35:06 8630 [Note] InnoDB: 9a0b16ac6bdf7fd69fe1ae1dfea7e72ff763aa8bd3f55b4446c2666bc73e62ec
2023-09-07 20:35:06 8630 [Note] InnoDB: c7846ce44859338691127a33f42f858d83bffed214f8c022c14463d30bdfee87
2023-09-07 20:35:06 8630 [Note] InnoDB: 846215c991a6a002e6fe4eae3f333bf8c19dc66adb297a12cbd7ae0c8488cd9e
2023-09-07 20:35:06 8630 [Note] InnoDB: b4912a98f64ec2807adacdee3d3705175b1d9b5dc1d26aa33148b52c5e682a15
2023-09-07 20:35:06 8630 [Note] InnoDB: e3d515d5e77a6bbe77b3c3bdf8b6e4f2763d268c1c0d431d98a804f8ed206a90
2023-09-07 20:35:06 8630 [Note] InnoDB: 9aac37a4fd702d7d3e127a45ce3fdd831f9defaaadcff6e2a10fde6667641091
2023-09-07 20:35:06 8630 [Note] InnoDB: 2cb2ef9bad8a3d095b2aefb3b393f067076d500f6f58d4e25b19e652e060a555
2023-09-07 20:35:06 8630 [Note] InnoDB: 21678789eb65c6bfe5fac5a3f38b51e3d0ef7e700a7a94b144083c9b31dfa281
2023-09-07 20:35:06 8630 [Note] InnoDB: 8c4ac93bcb359862c9e49dfcfffed3ccffb0a4b1598cc811b6d264d631105c46
2023-09-07 20:35:06 8630 [Note] InnoDB: 55827cc243d6f581cef948e8380937fe63bbf82f37816b42121ca0b85c869784
2023-09-07 20:35:06 8630 [Note] InnoDB: b2899e6b2da51d6387fe7afe852e0d24fcc1ec247cf3f06071b8b968dd5c530b
2023-09-07 20:35:06 8630 [Note] InnoDB: 63a1eb60b3087540ec547b6b48161db36a6fde0e4c5c153f4ec7dedf4cd1e1a1
2023-09-07 20:35:06 8630 [Note] InnoDB: 2520f03805ad9461761942ab405b04c1de6ab353137ff8b4e958f6842b897c14
2023-09-07 20:35:06 8630 [Note] InnoDB: 6c844f060fb2145f78c26aad2865adf94642c749b8b33f45424e5561d92b1715
2023-09-07 20:35:06 8630 [Note] InnoDB: c1616ad15445258f491cdb75c7d96597ff47b393f04a3aeeee1fd5656f6ba9da
2023-09-07 20:35:06 8630 [Note] InnoDB: 5d72e08a0acdc9b7cb8c76d2eda045bcd9f8beed982b727f7b32f7515ac2720d
2023-09-07 20:35:06 8630 [Note] InnoDB: 52e8aa9486c6cf8cdd831dd40663ff8ed296d4fddcecb0573fee1ee0f7973002
2023-09-07 20:35:06 8630 [Note] InnoDB: fba05dcab05c46a24da5b539152b6abb8808eb7794ce2fc78dc3bffdf6147cc7
2023-09-07 20:35:06 8630 [Note] InnoDB: edec489380cc09a5c9808c5660e19550d1a85da5fff9d9e10fb714030cb69cdd
2023-09-07 20:35:06 8630 [Note] InnoDB: b2c8536b3f18b04ace141f31b889fcbaee2fc78dc3bff5ef3decd16d00839714
2023-09-07 20:35:06 8630 [Note] InnoDB: 447585954ed1c764db1b03b079060b88e552e8fe3f591b07ce66005c20132000
2023-09-07 20:35:06 8630 [Note] InnoDB: 8000000000005628800000000000000a66696c65732f43726561746976652f63
2023-09-07 20:35:06 8630 [Note] InnoDB: 68617274732f5072656d69756d2d566563746f722d49636f6e2d4c6962726172
2023-09-07 20:35:06 8630 [Note] InnoDB: 792f52657461696c2d49636f6e732f5356472f4c696768742f53686f7070696e
2023-09-07 20:35:06 8630 [Note] InnoDB: 67204261672030312e7376673531613961363537316339306461653632646561
2023-09-07 20:35:06 8630 [Note] InnoDB: 36663232353431333831623280000000000055e153686f7070696e6720426167
2023-09-07 20:35:06 8630 [Note] InnoDB: 2030312e737667800000000000001280000000000000078000000000000cd280
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000005f2b3ce8800000005f2b3ce88000000080000000000000003936663932
2023-09-07 20:35:06 8630 [Note] InnoDB: 6638326339383362636661393533353066643463386431653138388000001b68
2023-09-07 20:35:06 8630 [Note] InnoDB: 0054200b20008000000000005629800000000000000a66696c65732f43726561
2023-09-07 20:35:06 8630 [Note] InnoDB: 746976652f6368617274732f5072656d69756d2d566563746f722d49636f6e2d
2023-09-07 20:35:06 8630 [Note] InnoDB: 4c6962726172792f52657461696c2d49636f6e732f5356472f4c696768742f4a
2023-09-07 20:35:06 8630 [Note] InnoDB: 6577656c72792e73766733636337313136343531313934633435346662383832
2023-09-07 20:35:06 8630 [Note] InnoDB: 3430616139356237653280000000000055e14a6577656c72792e737667800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 000000001280000000000000078000000000000f64800000005f2b3cea800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 005f2b3cea800000008000000000000000643663396339333464333535653032
2023-09-07 20:35:06 8630 [Note] InnoDB: 35396239363035396135326434373538388000001b6a005a2011200080000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000562a800000000000000a66696c65732f43726561746976652f6368617274
2023-09-07 20:35:06 8630 [Note] InnoDB: 732f5072656d69756d2d566563746f722d49636f6e2d4c6962726172792f5265
2023-09-07 20:35:06 8630 [Note] InnoDB: 7461696c2d49636f6e732f5356472f4c696768742f53686f7070696e67204361
2023-09-07 20:35:06 8630 [Note] InnoDB: 72742e7376676361663335663463373366326563346465626439346262343437
2023-09-07 20:35:06 8630 [Note] InnoDB: 61353636393580000000000055e153686f7070696e6720436172742e73766780
2023-09-07 20:35:06 8630 [Note] InnoDB: 00000000000012800000000000000780000000000011e6800000005f2b3ce880
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000005f2b3ce880000000800000000000000030303232313361306537303436
2023-09-07 20:35:06 8630 [Note] InnoDB: 646638363832393434623334666662366435658000001b6c005c201320008000
2023-09-07 20:35:06 8630 [Note] InnoDB: 00000000562b800000000000000a66696c65732f43726561746976652f636861
2023-09-07 20:35:06 8630 [Note] InnoDB: 7274732f5072656d69756d2d566563746f722d49636f6e2d4c6962726172792f
2023-09-07 20:35:06 8630 [Note] InnoDB: 52657461696c2d49636f6e732f5356472f4c696768742f57616c6c657420616e
2023-09-07 20:35:06 8630 [Note] InnoDB: 6420436172642e73766739343635616535373438303831336461323835306131
2023-09-07 20:35:06 8630 [Note] InnoDB: 3833316664313161383680000000000055e157616c6c657420616e6420436172
2023-09-07 20:35:06 8630 [Note] InnoDB: 642e737667800000000000001280000000000000078000000000000dfa800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 005f2b3ce8800000005f2b3ce880000000800000000000000033306364383633
2023-09-07 20:35:06 8630 [Note] InnoDB: 343130376234353738656135323433633865346565643237398000001b6e005b
2023-09-07 20:35:06 8630 [Note] InnoDB: 20122000800000000000562c800000000000000a66696c65732f437265617469
2023-09-07 20:35:06 8630 [Note] InnoDB: 76652f6368617274732f5072656d69756d2d566563746f722d49636f6e2d4c69
2023-09-07 20:35:06 8630 [Note] InnoDB: 62726172792f52657461696c2d49636f6e732f5356472f4c696768742f436173
2023-09-07 20:35:06 8630 [Note] InnoDB: 6820526566756e642030322e7376676664356235373234353163306661396162
2023-09-07 20:35:06 8630 [Note] InnoDB: 61366232393663353837666464333380000000000055e1436173682052656675
2023-09-07 20:35:06 8630 [Note] InnoDB: 6e642030322e7376678000000000000012800000000000000780000000000019
2023-09-07 20:35:06 8630 [Note] InnoDB: b1800000005f2b3cea800000005f2b3cea800000008000000000000000386537
2023-09-07 20:35:06 8630 [Note] InnoDB: 3935663466633339623531653432626164376138376339643766643031800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 1b700055200c2000800000000000562d800000000000000a66696c65732f4372
2023-09-07 20:35:06 8630 [Note] InnoDB: 6561746976652f6368617274732f5072656d69756d2d566563746f722d49636f
2023-09-07 20:35:06 8630 [Note] InnoDB: 6e2d4c6962726172792f52657461696c2d49636f6e732f5356472f4c69676874
2023-09-07 20:35:06 8630 [Note] InnoDB: 2f5368697070696e672e73766766643639333862326463323136373361353539
2023-09-07 20:35:06 8630 [Note] InnoDB: 3730396233323362326461653780000000000055e15368697070696e672e7376
2023-09-07 20:35:06 8630 [Note] InnoDB: 678000000000000012800000000000000780000000000011f4800000005f2b3c
2023-09-07 20:35:06 8630 [Note] InnoDB: e8800000005f2b3ce88000000080000000000000003135656363363038663331
2023-09-07 20:35:06 8630 [Note] InnoDB: 6365356631623133396265386163316566653034638000001b720058200f2000
2023-09-07 20:35:06 8630 [Note] InnoDB: 800000000000562e800000000000000a66696c65732f43726561746976652f63
2023-09-07 20:35:06 8630 [Note] InnoDB: 68617274732f5072656d69756d2d566563746f722d49636f6e2d4c6962726172
2023-09-07 20:35:06 8630 [Note] InnoDB: 792f52657461696c2d49636f6e732f5356472f4c696768742f53616c65204261
2023-09-07 20:35:06 8630 [Note] InnoDB: 736b65742e737667303239323932383537623966653562386266616531643930
2023-09-07 20:35:06 8630 [Note] InnoDB: 313466343061636480000000000055e153616c65204261736b65742e73766780
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000001280000000000000078000000000001047800000005f2b3cea80
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000005f2b3cea80000000800000000000000033656564643534343634343731
2023-09-07 20:35:06 8630 [Note] InnoDB: 326335353830646439643237303265393635398000001b740059201020008000
2023-09-07 20:35:06 8630 [Note] InnoDB: 00000000562f800000000000000a66696c65732f43726561746976652f636861
2023-09-07 20:35:06 8630 [Note] InnoDB: 7274732f5072656d69756d2d566563746f722d49636f6e2d4c6962726172792f
2023-09-07 20:35:06 8630 [Note] InnoDB: 52657461696c2d49636f6e732f5356472f4c696768742f447265737320536869
2023-09-07 20:35:06 8630 [Note] InnoDB: 7274732e73766763383262323264363563366635623933623032366461616239
2023-09-07 20:35:06 8630 [Note] InnoDB: 3137376132333880000000000055e14472657373205368697274732e73766780
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000001280000000000000078000000000001202800000005f2b3ce880
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000005f2b3ce880000000800000000000000035646562323866313563396134
2023-09-07 20:35:06 8630 [Note] InnoDB: 333139383435346333646161663635623437318000001b760054200b20008000
2023-09-07 20:35:06 8630 [Note] InnoDB: 000000005630800000000000000a66696c65732f43726561746976652f636861
2023-09-07 20:35:06 8630 [Note] InnoDB: 7274732f5072656d69756d2d566563746f722d49636f6e2d4c6962726172792f
2023-09-07 20:35:06 8630 [Note] InnoDB: 52657461696c2d49636f6e732f5356472f4c696768742f48616e676572732e73
2023-09-07 20:35:06 8630 [Note] InnoDB: 7667373737383832333438646564316366643163663364313562346233616663
2023-09-07 20:35:06 8630 [Note] InnoDB: 323480000000000055e148616e676572732e7376678000000000000012800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 00000000078000000000000e63800000005f2b3cea800000005f2b3cea800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0080000000000000003736663838666132626637616166373364336431343339
2023-09-07 20:35:06 8630 [Note] InnoDB: 3630663661373538648000001b00000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000000000000000800000000000000000000000008000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000800000000000000000000000008000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000800000000000000000000000008000000000000000000000000080
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000008000000000000000000000000080000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000008000000000000000000000000080000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 8000000000000000000000000080000000000000000000000000800000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000080000000000000000000000000800000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0080000000000000000000000000800000000000000000000000008000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000800000000000000000000000008000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000800000000000000000000000008000000000000000000000000080000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000008000000000000000000000000080000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000008000000000000000000000000080000000000000000000000000800000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000080000000000000000000000000800000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000080000000000000000000000000800000000000000000000000008000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000800000000000000000000000008000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000800000000000000000000000008000000000000000000000000080
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000000000008000000000000000000000000080000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000008000000000000000000000000080000000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 8000000000000000000000000080000000000000000000000000800000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000080000000000000000000000000800000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0080000000000000000000000000800000000000000000000000008000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000800000000000000000000000008000000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000800000000000000000000000008000000000000000000000000080000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 0000000000000000008000000000000000000000000080000000000000000000
2023-09-07 20:35:06 8630 [Note] InnoDB: 000000800000000000003e033cf23be33ada39c538ae379b7694357d346c335b
2023-09-07 20:35:06 8630 [Note] InnoDB: 7252313b301a2f036df62cdf2bde2acf69ce28bb27aa269365822469235c2255
2023-09-07 20:35:06 8630 [Note] InnoDB: 614c20391f231e175d031bf11add19cd58c717b516b315a3548d137f126f1171
2023-09-07 20:35:06 8630 [Note] InnoDB: 505b0f510e3b0d2f4c1d0b070a07090147f106e305db04c743b1029f01990083
2023-09-07 20:35:06 8630 [Note] InnoDB: End of page dump
2023-09-07 20:35:06 8630 [ERROR] InnoDB: File './database/data_table.ibd' is corrupted
2023-09-07 20:35:06 8630 [Note] InnoDB:  You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-09-07 20:35:06 8630 [ERROR] InnoDB: We detected index corruption in an InnoDB type table. You have to dump + drop + reimport the table or, in a case of widespread corruption, dump all InnoDB tables and recreate the whole tablespace. If the mariadbd server crashes after the startup or when you dump the tables. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-09-07 20:35:06 8630 [ERROR] mariadbd: Index for table 'data_table' is corrupt; try to repair it

Message #83 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Timothy Pearson <tpearson@raptorengineering.com>

To: 1032104 <1032104@bugs.debian.org>

Subject: Status update

Date: Tue, 7 Nov 2023 10:46:18 -0600 (CST)

I have traced this to a regression in the Linux kernel.  The issue appears to be a type of data race that is more likely to occur on ppc64el than on other architectures, but is also likely to affect other architectures.  The issue remains in the latest GIT version of the Linux kernel, and I am working with both upstream and our internal resources to try to isolate the root cause and generate a fix.

In the interim, disabling the io_uring subsystem will allow mariadb to function normally.  Given the nature of the kernel bug, I would recommend disabling io_uring entirely in the kernel configuration for affected systems, as other applications may also be impacted by the data corruption.

Message #104 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Timothy Pearson <tpearson@raptorengineering.com>

To: Timothy Pearson <tpearson@raptorengineering.com>, 1032104 <1032104@bugs.debian.org>

Subject: Re: Bug#1032104: Status update

Date: Mon, 13 Nov 2023 23:22:38 -0600 (CST)

I have traced this bug to a missing memory barrier in the powerpc IPI handling code.  io_uring uses task_work_add() to schedule I/O worker creation, which in turn issues an IPI, and when precise timing conditions are met the inconsistent state between the two CPU cores can lead to corruption of userspace data in RAM.

I have sent a patch upstream, and created a merge request for Debian here:

https://salsa.debian.org/kernel-team/linux/-/merge_requests/907

Message #117 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Timothy Pearson <tpearson@raptorengineering.com>

To: 1032104 <1032104@bugs.debian.org>

Date: Sat, 18 Nov 2023 18:05:48 -0600 (CST)

Root cause found, merge request here: https://salsa.debian.org/kernel-team/linux/-/merge_requests/917

Message #126 received at 1032104-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1032104-close@bugs.debian.org

Subject: Bug#1032104: fixed in linux 6.6.4-1~exp1

Date: Sun, 03 Dec 2023 20:48:02 +0000

Source: linux
Source-Version: 6.6.4-1~exp1
Done: Bastian Blank <waldi@debian.org>

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1032104@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank <waldi@debian.org> (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 20:57:56 +0100
Source: linux
Architecture: source
Version: 6.6.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Bastian Blank <waldi@debian.org>
Closes: 1032104 1037938
Changes:
 linux (6.6.4-1~exp1) experimental; urgency=medium
 .
   * New upstream stable update:
     https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.4
     - nvmet: nul-terminate the NQNs passed in the connect command
       (CVE-2023-6121)
 .
   [ Bastian Blank ]
   * Fix build dependency on rsync.
   * Fix build dependency on kernel-wedge.
   * udeb: Make i2c-hid modules optional.
 .
   [ Timothy Pearson ]
   * [powerpc] Don't clobber f0/vs0 during fp|altivec register save
     (Closes: #1032104)
 .
   [ Johannes Schauer Marin Rodrigues ]
   * Fix FTCBFS: Pass _PYTHON_SYSCONFIGDATA_NAME to the perf build.
     (Closes: #1037938) Thanks to Helmut Grohne for the patch.
Checksums-Sha1:
 bbef175fb0e0acdf376b47ead3e0b501b536b7ba 233463 linux_6.6.4-1~exp1.dsc
 b38f79198036fde7abf99f60ffba545b91cdf82c 142637188 linux_6.6.4.orig.tar.xz
 c9c7ff3da91737365776a70f2214444de0ce95b4 1558788 linux_6.6.4-1~exp1.debian.tar.xz
 1af076e46f3dc867fca2e895233423b4839007d0 5930 linux_6.6.4-1~exp1_source.buildinfo
Checksums-Sha256:
 b4f661d17aa7c10ed351b18fae004844a40cc8ba592f12fa6fe89f73d861846d 233463 linux_6.6.4-1~exp1.dsc
 13cc9a0a341c415acc759d642ae43c39645d00531b44725486f077747237301f 142637188 linux_6.6.4.orig.tar.xz
 c2a55c3f2aa20e85c4e2f4e42f0ef30e4509bb372fa49d8d9e64cd9893c7c391 1558788 linux_6.6.4-1~exp1.debian.tar.xz
 993b2f9fca42146cb58df83feb8d22cfccb8617a96e3b6e6d07d8f375154b1bc 5930 linux_6.6.4-1~exp1_source.buildinfo
Files:
 7d79fb0706acad7ec6db8ba7c4facd38 233463 kernel optional linux_6.6.4-1~exp1.dsc
 0203020079fe29e661809eeee5280e7e 142637188 kernel optional linux_6.6.4.orig.tar.xz
 408e780433e84019f962a1380f0a1f7b 1558788 kernel optional linux_6.6.4-1~exp1.debian.tar.xz
 f8bf11b8f04e3e6c5751a2b62111c644 5930 kernel optional linux_6.6.4-1~exp1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQ8pEKDNIgQDAQDOBFji0aBW7swjwUCZWzfQwAKCRBji0aBW7sw
j/hWAQDzAKGYNrjDHiGdhJnuoRH35w9VE7K5sW4m+KvbBq0qhwEAydEdh34ZpQAB
izRCFMEFyNzZY2J4b0Wup8D2z9FOaQA=
=vYsM
-----END PGP SIGNATURE-----

Message #131 received at 1032104@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: 1032104@bugs.debian.org

Subject: Fixed in 4.19.301, 5.10.203, 6.1.66

Date: Fri, 8 Dec 2023 09:56:21 +0100

So the fix landed as well in 5.10.203 and 6.1.66 in particular, will
add a respective closer for this bug with those rebases. This means
the update will be in the next upload rebasing at least to those
versions (it was too late for the next round of point release for
bookworm).

Message #136 received at 1032104-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1032104-close@bugs.debian.org

Subject: Bug#1032104: fixed in linux 6.1.66-1

Date: Sat, 09 Dec 2023 17:56:32 +0000

Source: linux
Source-Version: 6.1.66-1
Done: Salvatore Bonaccorso <carnil@debian.org>

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1032104@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso <carnil@debian.org> (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 09 Dec 2023 16:48:39 +0100
Source: linux
Architecture: source
Version: 6.1.66-1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Salvatore Bonaccorso <carnil@debian.org>
Closes: 1032104 1057790 1057843
Changes:
 linux (6.1.66-1) bookworm; urgency=medium
 .
   * New upstream stable update:
     https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.65
     - afs: Fix afs_server_list to be cleaned up with RCU
     - afs: Make error on cell lookup failure consistent with OpenAFS
     - [arm64,armhf] drm/panel: simple: Fix Innolux G101ICE-L01 bus flags
     - [arm64,armhf] drm/panel: simple: Fix Innolux G101ICE-L01 timings
     - wireguard: use DEV_STATS_INC()
     - ata: pata_isapnp: Add missing error check for devm_ioport_map()
     - [x86] drm/i915: do not clean GT table on error path
     - [arm64,armhf] drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP
       full
     - HID: fix HID device resource race between HID core and debugging support
     - ipv4: Correct/silence an endian warning in __ip_do_redirect
     - net: usb: ax88179_178a: fix failed operations during ax88179_reset
     - net/smc: avoid data corruption caused by decline
     - [armhf] arm/xen: fix xen_vcpu_info allocation alignment
     - [amd64,arm64] amd-xgbe: handle corner-case during sfp hotplug
     - [amd64,arm64] amd-xgbe: handle the corner-case during tx completion
     - [amd64,arm64] amd-xgbe: propagate the correct speed and duplex status
     - afs: Return ENOENT if no cell DNS record can be found
     - afs: Fix file locking on R/O volumes to operate in local mode
     - mm,kfence: decouple kfence from page granularity mapping judgement
     - i40e: use ERR_PTR error print in i40e messages
     - i40e: Fix adding unsupported cloud filters
     - [arm64] USB: dwc3: qcom: fix resource leaks on probe deferral
     - [arm64] USB: dwc3: qcom: fix ACPI platform device leak
     - lockdep: Fix block chain corruption
     - cifs: minor cleanup of some headers
     - smb3: allow dumping session and tcon id to improve stats analysis and
       debugging
     - cifs: print last update time for interface list
     - cifs: distribute channels across interfaces based on speed
     - cifs: account for primary channel in the interface list
     - cifs: fix leak of iface for primary channel
     - ext4: add a new helper to check if es must be kept
     - ext4: factor out __es_alloc_extent() and __es_free_extent()
     - ext4: use pre-allocated es in __es_insert_extent()
     - ext4: use pre-allocated es in __es_remove_extent()
     - ext4: using nofail preallocation in ext4_es_remove_extent()
     - ext4: using nofail preallocation in ext4_es_insert_delayed_block()
     - ext4: using nofail preallocation in ext4_es_insert_extent()
     - ext4: fix slab-use-after-free in ext4_es_insert_extent()
     - ext4: make sure allocate pending entry not fail
     - NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update()
     - NFSD: Fix checksum mismatches in the duplicate reply cache
     - ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA
     - swiotlb-xen: provide the "max_mapping_size" method
     - bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in
       btree_gc_coalesce()
     - md: fix bi_status reporting in md_end_clone_io
     - bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race
     - io_uring/fs: consider link->flags when getting path for LINKAT
     - [s390x] dasd: protect device queue against concurrent access
     - USB: serial: option: add Luat Air72*U series products
     - hv_netvsc: fix race of netvsc and VF register_netdevice
     - hv_netvsc: Fix race of register_netdevice_notifier and VF register
     - hv_netvsc: Mark VF as slave before exposing it to user-mode
     - dm-delay: fix a race between delay_presuspend and delay_bio
     - bcache: check return value from btree_node_alloc_replacement()
     - bcache: prevent potential division by zero error
     - bcache: fixup init dirty data errors
     - bcache: fixup lock c->root error
     - USB: serial: option: add Fibocom L7xx modules
     - USB: serial: option: fix FM101R-GL defines
     - USB: serial: option: don't claim interface 4 for ZTE MF290
     - usb: typec: tcpm: Skip hard reset when in error recovery
     - [arm64,armhf] USB: dwc2: write HCINT with INTMASK applied
     - [arm64,armhf] usb: dwc3: Fix default mode initialization
     - [arm64,armhf] usb: dwc3: set the dma max_seg_size
     - [arm64] USB: dwc3: qcom: fix software node leak on probe errors
     - [arm64] USB: dwc3: qcom: fix wakeup after probe deferral
     - io_uring: fix off-by one bvec index
     https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.66
     - cifs: Fix FALLOC_FL_ZERO_RANGE by setting i_size if EOF moved
     - cifs: Fix FALLOC_FL_INSERT_RANGE by setting i_size after EOF moved
     - smb: client: report correct st_size for SMB and NFS symlinks
     - pinctrl: avoid reload of p state in list iteration
     - firewire: core: fix possible memory leak in create_units()
     - mmc: sdhci-pci-gli: Disable LPM during initialization
     - mmc: cqhci: Increase recovery halt timeout
     - mmc: cqhci: Warn of halt or task clear failure
     - mmc: cqhci: Fix task clearing in CQE error recovery
     - mmc: block: Retry commands in CQE error recovery
     - mmc: block: Do not lose cache flush during CQE error recovery
     - mmc: block: Be sure to wait while busy in CQE error recovery
     - ALSA: hda: Disable power-save on KONTRON SinglePC
     - ALSA: hda/realtek: Headset Mic VREF to 100%
     - ALSA: hda/realtek: Add supported ALC257 for ChromeOS
     - dm-verity: align struct dm_verity_fec_io properly
     - scsi: Change SCSI device boolean fields to single bit flags
     - scsi: sd: Fix system start for ATA devices
     - drm/amd: Enable PCIe PME from D3
     - drm/amdgpu: Force order between a read and write to the same address
     - drm/amd/display: Include udelay when waiting for INBOX0 ACK
     - drm/amd/display: Remove min_dst_y_next_start check for Z8
     - drm/amd/display: Use DRAM speed from validation for dummy p-state
     - drm/amd/display: Update min Z8 residency time to 2100 for DCN314
     - drm/amd/display: fix ABM disablement
     - dm verity: initialize fec io before freeing it
     - dm verity: don't perform FEC for failed readahead IO
     - nvme: check for valid nvme_identify_ns() before using it
     - [x86] cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch()
     - dma-buf: fix check in dma_resv_add_fence
     - bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
     - [amd64] iommu/vt-d: Add MTL to quirk list to skip TE disabling
     - [powerpc*] KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user
       registers
     - [powerpc*] Don't clobber f0/vs0 during fp|altivec register save
       (Closes: #1032104)
     - btrfs: add dmesg output for first mount and last unmount of a filesystem
     - btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
     - btrfs: fix off-by-one when checking chunk map includes logical address
     - btrfs: send: ensure send_fd is writable
     - btrfs: make error messages more clear when getting a chunk map
     - btrfs: fix 64bit compat send ioctl arguments not initializing version
       member
     - Input: xpad - add HyperX Clutch Gladiate Support
     - wifi: cfg80211: fix CQM for non-range use
     - [arm64,armhf] USB: xhci-plat: fix legacy PHY double init
     - USB: core: Change configuration warnings to notices
     - usb: config: fix iteration issue in 'usb_get_bos_descriptor()'
     - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet
     - [arm64] dpaa2-eth: increase the needed headroom to account for alignment
     - net: stmmac: xgmac: Disable FPE MMC interrupts
     - r8169: prevent potential deadlock in rtl8169_close
     - [x86] KVM: x86: Fix lapic timer interrupt lost after loading a snapshot.
     - PCI: Lengthen reset delay for VideoPropulsion Torrent QN16e card
     - spi: Fix null dereference on suspend
     - drm/amd/display: Restore rptr/wptr for DMCUB as workaround
     - drm/amd/display: Guard against invalid RPTR/WPTR being set
     - [armhf] cpufreq: imx6q: don't warn for disabling a non-existing frequency
     - [armhf] cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily
     - [amd64] iommu/vt-d: Omit devTLB invalidation requests when TES=0
     - [amd64] iommu/vt-d: Allocate pasid table in device probe path
     - [amd64] iommu/vt-d: Add device_block_translation() helper
     - [amd64] iommu/vt-d: Disable PCI ATS in legacy passthrough mode
     - [amd64] iommu/vt-d: Make context clearing consistent with context mapping
     - drm/amd/pm: fix a memleak in aldebaran_tables_init
     - mmc: core: add helpers mmc_regulator_enable/disable_vqmmc
     - mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled
     - drm/amd/display: Expand kernel doc for DC
     - drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut
     - drm/amd/display: Fix the delta clamping for shaper LUT
     - drm/amd/display: Fix MPCC 1DLUT programming
     - r8169: disable ASPM in case of tx timeout
     - r8169: fix deadlock on RTL8125 in jumbo mtu mode (Closes: #1057790)
     - xen: Allow platform PCI interrupt to be shared
     - xen: simplify evtchn_do_upcall() call maze
     - [x86] xen: fix percpu vcpu_info allocation
     - [x86] apic/msi: Fix misconfigured non-maskable MSI quirk
     - iomap: update ki_pos a little later in iomap_dio_complete
       (Closes: #1057843)
 .
   [ Salvatore Bonaccorso ]
   * Bump ABI to 15
   * [rt] Update to 6.1.66-rt19
Checksums-Sha1:
 75d087cfc109545360cb85628ca2068a656f58bf 290924 linux_6.1.66-1.dsc
 bec397772676a6f06e2fde4c2328bcdc0beaea06 137491816 linux_6.1.66.orig.tar.xz
 af301e107224490faeda530343f96f17c0684f71 1580256 linux_6.1.66-1.debian.tar.xz
 348664cfbc75b567cf6256557f0c3d09fc8f7997 7065 linux_6.1.66-1_source.buildinfo
Checksums-Sha256:
 769e7dae9fe82bc29b55eb606fda6b0cc6221294a2ba3d7e7fcc78de84683f61 290924 linux_6.1.66-1.dsc
 71edfafca7cd8eaae26a8d29c1091bd39cfc2d196de38570b159c94f0d3e1ad5 137491816 linux_6.1.66.orig.tar.xz
 907af29ab9ff38594df378ba5c60619110389b92ba2a09a21adc0382f76e0240 1580256 linux_6.1.66-1.debian.tar.xz
 342dddfc2e87c8e8211e130e19253e23c1f5952036f29b4c9a7f9273c074d94a 7065 linux_6.1.66-1_source.buildinfo
Files:
 505a701b509c26df837dc4a6ff0f0844 290924 kernel optional linux_6.1.66-1.dsc
 ea8af00da46c0f6392324e83554102a2 137491816 kernel optional linux_6.1.66.orig.tar.xz
 307f584ef754457e172ad498979cba6c 1580256 kernel optional linux_6.1.66-1.debian.tar.xz
 2f1f205c788b2a730a7e7a89145dbf7d 7065 kernel optional linux_6.1.66-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmV0kZ5fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ErmUP/RZZN1ZMRy2nqQWPqXDrMUci6fOWcUCj
ZPAH/B9D9/+FYyRylJz8NENzJj82ZfNAUdKNMG0odp85pe6UOwvi6qMVIrsM3UrB
AQEbzEA0CS8XSTD2qdmOe2EaWHi0LvnopIQRGFy5Z3auQOk+EADbibRi2qZjM0Te
+Y1++jfXXLjbY5o+2oJMzaxZLBYRBcQizWfRKWjX4tmwcAZppABFShB5XEBlbeKx
8TZ6HhacpW3UImc1CTi8wFeO3T27bn4HQ9mLeW5vLh8bzbB3wnzmFzOn2wJj8Qf8
lRe6+oolFewZ57hBJjvDoK4CwQ9hapwPMJpAaG1NpE4QXIAAapb3OD5DP8vpsoTQ
bORrs3kvDRCA1ooCmGaEW7JBlolLl/mMxrIR4yGMzkXnA37UmAJ/PfmAJJO81J+H
cAhHdicTGrs6KQfNBBQzHC9vBJZNJ3Z5PpAXUncGQUDRueEz9kJXdwzZDkOf5DCC
JHrBXn7EZQLANXTeCg0za6/29VwURbSmUWXLk914sHb4xEPO/ivOpZAT8baB0JTV
hF8J6rzTyqsbv7gOFgOgrCCCvh5XU9Nvl7W3mRIHwiCdBKr39goL2V1S08kt0bmS
RLW+46T5U3Flcr5UGoIoEoBsav16aaHfaQ7mx182GGoAJqUf6tM4PuC4mDt1W4pQ
4o6djxs85N9S
=gQo4
-----END PGP SIGNATURE-----

Message #141 received at 1032104-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1032104-close@bugs.debian.org

Subject: Bug#1032104: fixed in linux 5.10.205-1

Date: Sun, 14 Jan 2024 19:48:12 +0000

Source: linux
Source-Version: 5.10.205-1
Done: Salvatore Bonaccorso <carnil@debian.org>

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1032104@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso <carnil@debian.org> (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2023 10:41:34 +0100
Source: linux
Architecture: source
Version: 5.10.205-1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Salvatore Bonaccorso <carnil@debian.org>
Closes: 1032104 1035587 1052304
Changes:
 linux (5.10.205-1) bullseye-security; urgency=high
 .
   * New upstream stable update:
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.198
     - NFS: Use the correct commit info in nfs_join_page_group()
     - NFS/pNFS: Report EINVAL errors from connect() to the server
     - SUNRPC: Mark the cred for revalidation if the server rejects it
     - tracing: Increase trace array ref count on enable and filter files
     - ata: ahci: Drop pointless VPRINTK() calls and convert the remaining ones
     - ata: libahci: clear pending interrupt status
     - ext4: remove the 'group' parameter of ext4_trim_extent
     - ext4: add new helper interface ext4_try_to_trim_range()
     - ext4: scope ret locally in ext4_try_to_trim_range()
     - ext4: change s_last_trim_minblks type to unsigned long
     - ext4: mark group as trimmed only if it was fully scanned
     - ext4: replace the traditional ternary conditional operator with with
       max()/min()
     - ext4: move setting of trimmed bit into ext4_try_to_trim_range()
     - ext4: do not let fstrim block system suspend
     - tracing: Have event inject files inc the trace array ref count
     - bpf: Avoid deadlock when using queue and stack maps from NMI
     - i40e: Fix VF VLAN offloading when port VLAN is configured
     - [powerpc*] perf/hv-24x7: Update domain value check
     - dccp: fix dccp_v4_err()/dccp_v6_err() again
     - [x86] platform/x86: intel_scu_ipc: Check status after timeout in
       busy_loop()
     - [x86] platform/x86: intel_scu_ipc: Check status upon timeout in
       ipc_wait_for_interrupt()
     - [x86] platform/x86: intel_scu_ipc: Don't override scu in
       intel_scu_ipc_dev_simple_command()
     - [x86] platform/x86: intel_scu_ipc: Fail IPC send if still busy
     - [x86] srso: Fix srso_show_state() side effect
     - [x86] srso: Fix SBPB enablement for spec_rstack_overflow=off
     - [arm64] net: hns3: only enable unicast promisc when mac table full
     - [arm64] net: hns3: add 5ms delay before clear firmware reset irq source
     - net: bridge: use DEV_STATS_INC()
     - team: fix null-ptr-deref when team device type is changed
     - seqlock: avoid -Wshadow warnings
     - seqlock: Rename __seqprop() users
     - seqlock: Prefix internal seqcount_t-only macros with a "do_"
     - locking/seqlock: Do the lockdep annotation before locking in
       do_write_seqcount_begin_nested()
     - bnxt_en: Flush XDP for bnxt_poll_nitroa0()'s NAPI
     - net: rds: Fix possible NULL-pointer dereference
     - gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
     - i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
     - Input: i8042 - rename i8042-x86ia64io.h to i8042-acpipnpio.h
     - Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
     - [arm64] media: venus: core: Add io base variables for each block
     - [arm64] media: venus: hfi,pm,firmware: Convert to block relative
       addressing
     - [arm64] media: venus: hfi: Define additional 6xx registers
     - [arm64] media: venus: core: Add differentiator IS_V6(core)
     - [arm64] media: venus: hfi: Add a 6xx boot logic
     - [arm64] media: venus: hfi_venus: Write to VIDC_CTRL_INIT after unmasking
       interrupts
     - netfilter: use actual socket sk for REJECT action
     - netfilter: nft_exthdr: Support SCTP chunks
     - netfilter: nf_tables: add and use nft_sk helper
     - netfilter: nf_tables: add and use nft_thoff helper
     - netfilter: nft_exthdr: break evaluation if setting TCP option fails
     - netfilter: exthdr: add support for tcp option removal
     - netfilter: nft_exthdr: Fix non-linear header modification
     - ata: libata: Rename link flag ATA_LFLAG_NO_DB_DELAY
     - ata: ahci: Add support for AMD A85 FCH (Hudson D4)
     - ata: ahci: Rename board_ahci_mobile
     - ata: ahci: Add Elkhart Lake AHCI controller
     - btrfs: reset destination buffer when read_extent_buffer() gets invalid
       range
     - [armhf] bus: ti-sysc: Use fsleep() instead of usleep_range() in
       sysc_reset()
     - [armhf] bus: ti-sysc: Fix missing AM35xx SoC matching
     - [armhf] ARM: dts: omap: correct indentation
     - [armhf] bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart
       wake-up
     - gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
     - i2c: npcm7xx: Fix callback completion ordering
     - scsi: qedf: Add synchronization between I/O completions and abort
     - ring-buffer: Avoid softlockup in ring_buffer_resize()
     - ring-buffer: Do not attempt to read past "commit"
     - scsi: pm80xx: Use phy-specific SAS address when sending PHY_START command
     - scsi: pm80xx: Avoid leaking tags when processing
       OPC_INB_SET_CONTROLLER_CONFIG command
     - ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
     - bpf: Clarify error expectations from bpf_clone_redirect
     - media: vb2: frame_vector.c: replace WARN_ONCE with a comment
     - [powerpc*] watchpoints: Disable preemption in thread_change_pc()
     - [armhf] ncsi: Propagate carrier gain/loss events to the NCSI controller
     - sched/cpuacct: Fix user/system in shown cpuacct.usage*
     - sched/cpuacct: Fix charge percpu cpuusage
     - sched/cpuacct: Optimize away RCU read lock
     - cgroup: Fix suspicious rcu_dereference_check() usage warning
     - ACPI: Check StorageD3Enable _DSD property in ACPI code
     - nvme-pci: factor the iod mempool creation into a helper
     - nvme-pci: factor out a nvme_pci_alloc_dev helper
     - nvme-pci: do not set the NUMA node of device if it has none
     - watchdog: iTCO_wdt: No need to stop the timer in probe
     - watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
     - netfilter: nft_exthdr: Search chunks in SCTP packets only
     - netfilter: nft_exthdr: Fix for unsafe packet data read
     - nvme-pci: always return an ERR_PTR from nvme_pci_alloc_dev
     - Revert "tty: n_gsm: fix UAF in gsm_cleanup_mux"
     - serial: 8250_port: Check IRQ data before use
     - nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
     - netfilter: nf_tables: disallow rule removal from chain binding
       (CVE-2023-5197)
     - ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre
       M70q
     - ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION
       CODES
     - i2c: i801: unregister tco_pdev in i801_probe() error path
     - Revert "SUNRPC dont update timeout value on connection reset"
     - proc: nommu: /proc/<pid>/maps: release mmap read lock
     - ring-buffer: Update "shortest_full" in polling
     - btrfs: properly report 0 avail for very full file systems
     - bpf: Fix BTF_ID symbol generation collision
     - bpf: Fix BTF_ID symbol generation collision in tools/
     - net: thunderbolt: Fix TCPv6 GSO checksum calculation
     - ata: libata-core: Fix ata_port_request_pm() locking
     - ata: libata-core: Fix port and device removal
     - ata: libata-core: Do not register PM operations for SAS ports
     - ata: libata-sata: increase PMP SRST timeout to 10s
     - fs: binfmt_elf_efpic: fix personality for ELF-FDPIC
     - NFS: Cleanup unused rpc_clnt variable
     - NFS: rename nfs_client_kset to nfs_kset
     - NFSv4: Fix a state manager thread deadlock regression
     - ring-buffer: remove obsolete comment for free_buffer_page()
     - ring-buffer: Fix bytes info in per_cpu buffer stats
     - rbd: move rbd_dev_refresh() definition
     - rbd: decouple header read-in from updating rbd_dev->header
     - rbd: decouple parent info read-in from updating rbd_dev
     - rbd: take header_rwsem in rbd_dev_refresh() only when updating
     - block: fix use-after-free of q->q_usage_counter
     - Revert "clk: imx: pll14xx: dynamically configure PLL for
       393216000/361267200Hz"
     - Revert "PCI: qcom: Disable write access to read only registers for IP
       v2.3.3"
     - scsi: zfcp: Fix a double put in zfcp_port_enqueue()
     - wifi: mwifiex: Fix tlv_buf_left calculation
     - net: replace calls to sock->ops->connect() with kernel_connect()
     - net: prevent rewrite of msg_name in sock_sendmsg()
     - [arm64] Add Cortex-A520 CPU part definition
     - ubi: Refuse attaching if mtd's erasesize is 0
     - wifi: iwlwifi: dbg_ini: fix structure packing
     - wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet
     - bpf: Fix tr dereferencing
     - drivers/net: process the result of hdlc_open() and add call of
       hdlc_close() in uhdlc_close()
     - wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling
     - regmap: rbtree: Fix wrong register marked as in-cache when creating new
       node
     - ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
     - scsi: target: core: Fix deadlock due to recursive locking
     - ima: rework CONFIG_IMA dependency block
     - NFSv4: Fix a nfs4_state_manager() race
     - modpost: add missing else to the "of" check
     - net: fix possible store tearing in neigh_periodic_work()
     - ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
     - [arm64,armhf] net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is
       absent
     - net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg
     - net: nfc: llcp: Add lock when modifying device list
     - net: ethernet: ti: am65-cpsw: Fix error code in
       am65_cpsw_nuss_init_tx_chns()
     - netfilter: handle the connecting collision properly in
       nf_conntrack_proto_sctp
     - netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure
     - [armhf] net: stmmac: dwmac-stm32: fix resume on STM32 MCU
     - tipc: fix a potential deadlock on &tx->lock
     - tcp: fix quick-ack counting to count actual ACKs of new data
     - tcp: fix delayed ACKs for MSS boundary condition
     - sctp: update transport state when processing a dupcook packet
     - sctp: update hb timer immediately after users change hb_interval
     - cpupower: add Makefile dependencies for install targets
     - dm zoned: free dmz->ddev array in dmz_put_zoned_devices
     - RDMA/core: Require admin capabilities to set system parameters
     - of: dynamic: Fix potential memory leak in of_changeset_action()
     - IB/mlx4: Fix the size of a buffer in add_port_entries()
     - [armhf] gpio: aspeed: fix the GPIO number passed to
       pinctrl_gpio_set_config()
     - RDMA/cma: Initialize ib_sa_multicast structure to 0 when join
     - RDMA/cma: Fix truncation compilation warning in make_cma_ports
     - RDMA/uverbs: Fix typo of sizeof argument
     - RDMA/siw: Fix connection failure handling
     - RDMA/mlx5: Fix NULL string error
     - netfilter: nf_tables: fix kdoc warnings after gc rework
     - netfilter: nftables: exthdr: fix 4-byte stack OOB write
     - xen/events: replace evtchn_rwlock with RCU (CVE-2023-34324)
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.199
     - RDMA/srp: Make struct scsi_cmnd and struct srp_request adjacent
     - RDMA/srp: Do not call scsi_done() from srp_abort()
     - RDMA/cxgb4: Check skb value for failure to allocate
     - [arm64] perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7
     - HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
     - quota: Fix slow quotaoff
     - net: prevent address rewrite in kernel_bind()
     - [arm64] drm/msm/dp: do not reinitialize phy unless retry during link
       training
     - [arm64] drm/msm/dsi: skip the wait for video mode done if not applicable
     - [arm64] drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid
       overflow
     - xen-netback: use default TX queue size for vifs
     - [x86] drm/vmwgfx: fix typo of sizeof argument
     - net: macsec: indicate next pn update when offloading
     - net: phy: mscc: macsec: reject PN update requests
     - ixgbe: fix crash with empty VF macvlan list
     - net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
     - nfc: nci: assert requested protocol is valid
     - workqueue: Override implicit ordered attribute in
       workqueue_apply_unbound_cpumask()
     - net: add sysctl accept_ra_min_rtr_lft
     - net: change accept_ra_min_rtr_lft to affect all RA lifetimes
     - net: release reference to inet6_dev pointer
     - [armhf] dmaengine: stm32-mdma: abort resume if no ongoing transfer
     - usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer
     - net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read
     - [arm64,armhf] usb: dwc3: Soft reset phy on probe for host
     - usb: musb: Get the musb_qh poniter after musb_giveback
     - usb: musb: Modify the "HWVers" register address
     - iio: pressure: bmp280: Fix NULL pointer exception
     - iio: pressure: dps310: Adjust Timeout Settings
     - iio: pressure: ms5611: ms5611_prom_is_valid false negative bug
     - [x86] cpu: Fix AMD erratum #1485 on Zen4-based CPUs
     - mcb: remove is_added flag from mcb_device struct
     - [x86] thunderbolt: Check that lane 1 is in CL0 before enabling lane
       bonding
     - libceph: use kernel_connect()
     - ceph: fix incorrect revoked caps assert in ceph_fill_file_size()
     - ceph: fix type promotion bug on 32bit systems
     - Input: powermate - fix use-after-free in powermate_config_complete
     - Input: psmouse - fix fast_reconnect function for PS/2 mode
     - Input: xpad - add PXN V900 support
     - Input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table
     - Input: goodix - ensure int GPIO is in input for gpio_count == 1 &&
       gpio_int_idx == 0 case
     - tee: amdtee: fix use-after-free vulnerability in amdtee_close_session
     - cgroup: Remove duplicates in cgroup v1 tasks file
     - pinctrl: avoid unsafe code pattern in find_pinctrl()
     - counter: microchip-tcb-capture: Fix the use of internal GCLK logic
     - usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
     - usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call
     - [powerpc*] 8xx: Fix pte_access_permitted() for PAGE_NONE
     - [powerpc*] 64e: Fix wrong test in __ptep_test_and_clear_young()
     - [x86] alternatives: Disable KASAN in apply_alternatives()
     - [arm64] report EL1 UNDEFs better
     - [arm64] die(): pass 'err' as long
     - [arm64] consistently pass ESR_ELx to die()
     - [arm64] rework FPAC exception handling
     - [arm64] rework BTI exception handling
     - [arm64] allow kprobes on EL0 handlers
     - [arm64] split EL0/EL1 UNDEF handlers
     - [arm64] factor out EL1 SSBS emulation hook
     - [arm64] factor insn read out of call_undef_hook()
     - [arm64] rework EL0 MRS emulation
     - [arm64] armv8_deprecated: fold ops into insn_emulation
     - [arm64] armv8_deprecated move emulation functions
     - [arm64] armv8_deprecated: move aarch32 helper earlier
     - [arm64] armv8_deprecated: rework deprected instruction handling
     - [arm64] armv8_deprecated: fix unused-function error
     - RDMA/srp: Set scmnd->result only when scmnd is not NULL
     - RDMA/srp: Fix srp_abort()
     - ravb: Fix use-after-free issue in ravb_tx_timeout_work() (CVE-2023-35827)
     - dev_forward_skb: do not scrub skb mark within the same name space
     - lib/Kconfig.debug: do not enable DEBUG_PREEMPT by default
     - mm/memory_hotplug: rate limit page migration warnings
     - Documentation: sysctl: align cells in second content column
     - usb: hub: Guard against accesses to uninitialized BOS descriptors
     - Bluetooth: hci_event: Ignore NULL link key
     - Bluetooth: Reject connection with the device which has same BD_ADDR
     - Bluetooth: Fix a refcnt underflow problem for hci_conn
     - Bluetooth: vhci: Fix race when opening vhci device
     - Bluetooth: hci_event: Fix coding style
     - Bluetooth: avoid memcmp() out of bounds warning
     - ice: fix over-shifted variable
     - ice: reset first in crash dump kernels
     - nfc: nci: fix possible NULL pointer dereference in send_acknowledge()
     - regmap: fix NULL deref on lookup
     - [x86] KVM: x86: Mask LVTPC when handling a PMI
     - [x86] sev: Disable MMIO emulation from user mode (CVE-2023-46813)
     - [x86] sev: Check IOBM for IOIO exceptions from user-space (CVE-2023-46813)
     - [x86] sev: Check for user-space IOIO pointing to kernel space
       (CVE-2023-46813)
     - tcp: check mptcp-level constraints for backlog coalescing
     - netfilter: nft_payload: fix wrong mac header matching
     - nvmet-tcp: Fix a possible UAF in queue intialization setup (CVE-2023-5178)
     - [x86] drm/i915: Retry gtt fault when out of fence registers
     - qed: fix LL2 RX buffer allocation
     - xfrm: fix a data-race in xfrm_gen_index()
     - xfrm: interface: use DEV_STATS_INC()
     - net: ipv4: fix return value check in esp_remove_trailer
     - net: ipv6: fix return value check in esp_remove_trailer
     - net: rfkill: gpio: prevent value glitch during probe
     - tcp: fix excessive TLP and RACK timeouts from HZ rounding
     - tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single
       skb
     - tun: prevent negative ifindex
     - ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr
     - net: usb: smsc95xx: Fix an error code in smsc95xx_reset()
     - i40e: prevent crash on probe if hw registers have invalid values
     - net: dsa: bcm_sf2: Fix possible memory leak in bcm_sf2_mdio_register()
     - net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve
     - netfilter: nft_set_rbtree: .deactivate fails if element has expired
     - net: pktgen: Fix interface flags printing
     - [x86] thunderbolt: Workaround an IOMMU fault on certain systems with Intel
       Maple Ridge
     - resource: Add irqresource_disabled()
     - ACPI: Drop acpi_dev_irqresource_disabled()
     - ACPI: resources: Add DMI-based legacy IRQ override quirk
     - ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA
     - ACPI: resource: Add ASUS model S5402ZA to quirks
     - ACPI: resource: Skip IRQ override on Asus Vivobook S5602ZA
     - ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks
     - ACPI: resource: Skip IRQ override on Asus Expertbook B2402CBA
     - ACPI: resource: Skip IRQ override on ASUS ExpertBook B1502CBA
     - ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CBA
     - usb: core: Track SuperSpeed Plus GenXxY
     - xhci: cleanup xhci_hub_control port references
     - xhci: move port specific items such as state completions to port structure
     - xhci: rename resume_done to resume_timestamp
     - xhci: clear usb2 resume related variables in one place.
     - xhci: decouple usb2 port resume and get_port_status request handling
     - xhci: track port suspend state correctly in unsuccessful resume cases
     - serial: 8250: omap: Fix imprecise external abort for omap_8250_pm()
     - serial: 8250_omap: Fix errors with no_console_suspend
     - drm/amd/display: only check available pipe to disable vbios mode.
     - drm/amd/display: Don't set dpms_off for seamless boot
     - drm/connector: Give connector sysfs devices there own device_type
     - drm/connector: Add a fwnode pointer to drm_connector and register with
       ACPI (v2)
     - drm/connector: Add drm_connector_find_by_fwnode() function (v3)
     - drm/connector: Add support for out-of-band hotplug notification (v3)
     - usb: typec: altmodes/displayport: Notify drm subsys of hotplug events
     - usb: typec: altmodes/displayport: Signal hpd low when exiting mode
     - ARM: dts: ti: omap: Fix noisy serial with overrun-throttle-ms for mapphone
     - btrfs: return -EUCLEAN for delayed tree ref with a ref count not equals to
       1
     - btrfs: initialize start_slot in btrfs_log_prealloc_extents
     - i2c: mux: Avoid potential false error message in i2c_mux_add_adapter
     - overlayfs: set ctime when setting mtime and atime
     - gpio: timberdale: Fix potential deadlock on &tgpio->lock
     - ata: libata-eh: Fix compilation warning in ata_eh_link_report()
     - tracing: relax trace_event_eval_update() execution with cond_resched()
     - HID: holtek: fix slab-out-of-bounds Write in holtek_kbd_input_event
     - Bluetooth: Avoid redundant authentication
     - Bluetooth: hci_core: Fix build warnings
     - wifi: cfg80211: Fix 6GHz scan configuration
     - wifi: mac80211: allow transmitting EAPOL frames with tainted key
     - wifi: cfg80211: avoid leaking stack data into trace
     - regulator/core: Revert "fix kobject release warning and memory leak in
       regulator_register()"
     - sky2: Make sure there is at least one frag_addr available
     - ipv4/fib: send notify when delete source address routes
     - drm: panel-orientation-quirks: Add quirk for One Mix 2S
     - btrfs: fix some -Wmaybe-uninitialized warnings in ioctl.c
     - HID: multitouch: Add required quirk for Synaptics 0xcd7e device
     - [x86] platform/x86: touchscreen_dmi: Add info for the Positivo C4128B
     - net/mlx5: Handle fw tracer change ownership event based on MTRC
     - Bluetooth: hci_event: Fix using memcmp when comparing keys
     - mtd: physmap-core: Restore map_rom fallback
     - mmc: core: sdio: hold retuning if sdio in 1-bit mode
     - mmc: core: Capture correct oemid-bits for eMMC cards
     - Revert "pinctrl: avoid unsafe code pattern in find_pinctrl()"
     - pNFS: Fix a hang in nfs4_evict_inode()
     - ACPI: irq: Fix incorrect return value in acpi_register_gsi()
     - nvme-pci: add BOGUS_NID for Intel 0a54 device
     - nvme-rdma: do not try to stop unallocated queues
     - USB: serial: option: add Telit LE910C4-WWX 0x1035 composition
     - USB: serial: option: add entry for Sierra EM9191 with new firmware
     - USB: serial: option: add Fibocom to DELL custom modem FM101R-GL
     - perf: Disallow mis-matched inherited group reads (CVE-2023-5717)
     - [s390x] pci: fix iommu bitmap allocation
     - [x86] platform/x86: asus-wmi: Change ASUS_WMI_BRN_DOWN code from 0x20 to
       0x2e
     - [x86] platform/x86: asus-wmi: Map 0x2a code, Ignore 0x2b and 0x2c events
     - Bluetooth: hci_sock: fix slab oob read in create_monitor_event
     - Bluetooth: hci_sock: Correctly bounds check and pad HCI_MON_NEW_INDEX name
     - xfrm6: fix inet6_dev refcount underflow problem
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.200
     - virtio_balloon: Fix endless deflation and inflation on arm64
     - virtio-mmio: fix memory leak of vm_dev
     - mm/page_alloc: correct start page when guard page debug is enabled
     - drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()
     - r8169: fix the KCSAN reported data-race in rtl_tx while reading
       TxDescArray[entry].opts1
     - r8169: fix the KCSAN reported data race in rtl_rx while reading
       desc->opts1
     - treewide: Spelling fix in comment
     - igb: Fix potential memory leak in igb_add_ethtool_nfc_entry
     - neighbour: fix various data-races
     - igc: Fix ambiguity in the ethtool advertising
     - net: ieee802154: adf7242: Fix some potential buffer overflow in
       adf7242_stats_show()
     - net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg
     - r8152: Increase USB control msg timeout to 5000ms as per spec
     - r8152: Run the unload routine if we have errors during probe
     - r8152: Cancel hw_phy_work if we have an error in probe
     - r8152: Release firmware if we have an error in probe
     - tcp: fix wrong RTO timeout when received SACK reneging
     - gtp: uapi: fix GTPA_MAX
     - gtp: fix fragmentation needed check with gso
     - i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR
     - [armhf] i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node()
     - [armhf] i2c: stm32f7: Fix PEC handling in case of SMBUS transfers
     - [armhf] i2c: aspeed: Fix i2c bus hang in slave read
     - tracing/kprobes: Fix the description of variable length arguments
     - [arm64,armhf] nvmem: imx: correct nregs for i.MX6ULL
     - [arm64,armhf] nvmem: imx: correct nregs for i.MX6SLL
     - [arm64,armhf] nvmem: imx: correct nregs for i.MX6UL
     - perf/core: Fix potential NULL deref
     - clk: Sanitize possible_parent_show to Handle Return Value of
       of_clk_get_parent_name
     - [x86] i8259: Skip probing when ACPI/MADT advertises PCAT compatibility
     - kobject: Fix slab-out-of-bounds in fill_kobj_path() (CVE-2023-45863)
     - f2fs: fix to do sanity check on inode type during garbage collection
       (CVE-2021-44879)
     - [x86] mm: Simplify RESERVE_BRK()
     - [x86] mm: Fix RESERVE_BRK() for older binutils
     - ext4: add two helper functions extent_logical_end() and pa_logical_end()
     - ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow
     - ext4: avoid overlapping preallocations due to overflow
     - [x86] objtool/x86: add missing embedded_insn check
     - driver: platform: Add helper for safer setting of driver_override
     - [arm64] rpmsg: Constify local variable in field store macro
     - rpmsg: Fix kfree() of static memory on setting driver_override
     - rpmsg: Fix calling device_lock() on non-initialized device
     - [arm64] rpmsg: glink: Release driver_override
     - [arm64] rpmsg: Fix possible refcount leak in
       rpmsg_register_device_override()
     - [x86] Fix .brk attribute in linker script
     - net: sched: cls_u32: Fix allocation size in u32_init()
     - [armhf] irqchip/stm32-exti: add missing DT IRQ flag translation
     - Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport
     - fbdev: atyfb: only use ioremap_uc() on i386 and ia64
     - netfilter: nfnetlink_log: silence bogus compiler warning
     - ASoC: rt5650: fix the wrong result of key button
     - [x86] fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()
     - scsi: mpt3sas: Fix in error path
     - net: chelsio: cxgb4: add an error code check in t4_load_phy_fw
     - [powerpc*] mm: Fix boot crash with FLATMEM
     - can: isotp: change error format from decimal to symbolic error names
     - can: isotp: add symbolic error message to isotp_module_init()
     - can: isotp: Add error message if txqueuelen is too small
     - can: isotp: set max PDU size to 64 kByte
     - can: isotp: isotp_bind(): return -EINVAL on incorrect CAN ID formatting
     - can: isotp: check CAN address family in isotp_bind()
     - can: isotp: handle wait_event_interruptible() return values
     - can: isotp: add local echo tx processing and tx without FC
     - can: isotp: isotp_bind(): do not validate unused address information
     - can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior
     - PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
     - usb: storage: set 1.50 as the lower bcdDevice for older "Super Top"
       compatibility
     - usb: raw-gadget: properly handle interrupted requests
     - tty: 8250: Remove UC-257 and UC-431
     - tty: 8250: Add support for additional Brainboxes UC cards
     - tty: 8250: Add support for Brainboxes UP cards
     - tty: 8250: Add support for Intashield IS-100
     - ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.201
     - [x86] iov_iter, x86: Be consistent about the __user tag on
       copy_mc_to_user()
     - sched/uclamp: Ignore (util == 0) optimization in feec() when p_util_max =
       0
     - vfs: fix readahead(2) on block devices
     - [x86] srso: Fix SBPB enablement for (possible) future fixed HW
     - futex: Don't include process MM in futex key on no-MMU
     - [x86] boot: Fix incorrect startup_gdt_descr.size
     - pstore/platform: Add check for kstrdup
     - genirq/matrix: Exclude managed interrupts in irq_matrix_allocated()
     - i40e: fix potential memory leaks in i40e_remove()
     - udp: add missing WRITE_ONCE() around up->encap_rcv
     - tcp: call tcp_try_undo_recovery when an RTOd TFO SYNACK is ACKed
     - overflow: Implement size_t saturating arithmetic helpers
     - gve: Use size_add() in call to struct_size()
     - tipc: Use size_add() in calls to struct_size()
     - wifi: rtw88: debug: Fix the NULL vs IS_ERR() bug for debugfs_create_file()
     - tcp_metrics: add missing barriers on delete
     - tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics()
     - tcp_metrics: do not create an entry from tcp_init_metrics()
     - wifi: rtlwifi: fix EDCA limit set by BT coexistence
     - can: dev: can_restart(): don't crash kernel if carrier is OK
     - can: dev: can_restart(): fix race condition between controller restart and
       netif_carrier_on()
     - PM / devfreq: rockchip-dfi: Make pmu regmap mandatory
     - thermal: core: prevent potential string overflow
     - r8169: use tp_to_dev instead of open code
     - r8169: fix rare issue with broken rx after link-down on RTL8125
     - tcp: fix cookie_init_timestamp() overflows
     - ACPI: sysfs: Fix create_pnp_modalias() and create_of_modalias()
     - ipv6: avoid atomic fragment on GSO packets
     - net: add DEV_STATS_READ() helper
     - ipvlan: properly track tx_errors
     - regmap: debugfs: Fix a erroneous check after snprintf()
     - [arm64] clk: qcom: clk-rcg2: Fix clock rate overflow for high parent
       frequencies
     - [arm64] clk: qcom: mmcc-msm8998: Add hardware clockgating registers to
       some clks
     - [arm64] clk: qcom: mmcc-msm8998: Don't check halt bit on some branch clks
     - [arm64] clk: qcom: mmcc-msm8998: Set bimc_smmu_gdsc always on
     - [arm64] clk: qcom: mmcc-msm8998: Fix the SMMU GDSC
     - [arm64] clk: qcom: gcc-sm8150: use ARRAY_SIZE instead of specifying
       num_parents
     - [arm64] clk: qcom: gcc-sm8150: Fix gcc_sdcc2_apps_clk_src
     - [arm64] clk: imx: imx8mq: correct error handling path
     - clk: asm9260: use parent index to link the reference clock
     - clk: linux/clk-provider.h: fix kernel-doc warnings and typos
     - [arm64] spi: nxp-fspi: use the correct ioremap function
     - [armhf] clk: ti: Add ti_dt_clk_name() helper to use clock-output-names
     - [armhf] clk: ti: Update pll and clockdomain clocks to use ti_dt_clk_name()
     - [armhf] clk: ti: Update component clocks to use ti_dt_clk_name()
     - [armhf] clk: ti: change ti_clk_register[_omap_hw]() API
     - [armhf] clk: ti: fix double free in of_ti_divider_clk_setup()
     - [x86] platform/x86: wmi: Fix probe failure when failing to register WMI
       devices
     - [x86] platform/x86: wmi: remove unnecessary initializations
     - [x86] platform/x86: wmi: Fix opening of char device
     - hwmon: (coretemp) Fix potentially truncated sysfs attribute name
     - [arm64,armhf] drm/rockchip: vop: Fix reset of state in duplicate state
       crtc funcs
     - [arm64,armhf] drm/rockchip: vop: Fix call to crtc reset helper
     - drm/radeon: possible buffer overflow
     - [arm64] drm/rockchip: cdn-dp: Fix some error handling paths in
       cdn_dp_probe()
     - [arm64,armhf] drm/rockchip: Fix type promotion bug in
       rockchip_gem_iommu_map()
     - xen-pciback: Consider INTx disabled when MSI/MSI-X is enabled
     - [arm64] dts: qcom: msm8916: Fix iommu local address range
     - [arm64] dts: qcom: sdm845-mtp: fix WiFi configuration
     - [i386] hwrng: geode - fix accessing registers
     - libnvdimm/of_pmem: Use devm_kstrdup instead of kstrdup and check its
       return value
     - nd_btt: Make BTT lanes preemptible
     - [arm64] crypto: caam/qi2 - fix Chacha20 + Poly1305 self test failure
     - [arm64] crypto: caam/jr - fix Chacha20 + Poly1305 self test failure
     - [x86] crypto: qat - mask device capabilities with soft straps
     - [x86] crypto: qat - increase size of buffers
     - hid: cp2112: Fix duplicate workqueue initialization
     - [armel,armhf] 9321/1: memset: cast the constant byte to unsigned char
     - ext4: move 'ix' sanity check to corrent position
     - IB/mlx5: Fix rdma counter binding for RAW QP
     - [arm64] RDMA/hns: Fix uninitialized ucmd in hns_roce_create_qp_common()
     - [arm64] RDMA/hns: Fix signed-unsigned mixed comparisons
     - scsi: ufs: core: Leave space for '\0' in utf8 desc string
     - [amd64] RDMA/hfi1: Workaround truncation compilation error
     - hid: cp2112: Fix IRQ shutdown stopping polling for all IRQs on chip
     - Revert "HID: logitech-hidpp: add a module parameter to keep firmware
       gestures"
     - HID: logitech-hidpp: Remove HIDPP_QUIRK_NO_HIDINPUT quirk
     - HID: logitech-hidpp: Don't restart IO, instead defer hid_connect() only
     - HID: logitech-hidpp: Revert "Don't restart communication if not necessary"
     - HID: logitech-hidpp: Move get_wireless_feature_index() check to
       hidpp_connect_event()
     - [x86] ASoC: Intel: Skylake: Fix mem leak when parsing UUIDs fails
     - padata: Convert from atomic_t to refcount_t on parallel_data->refcnt
     - padata: Fix refcnt handling in padata_free_shell()
     - mfd: core: Un-constify mfd_cell.of_reg
     - mfd: core: Ensure disabled devices are skipped without aborting
     - mfd: dln2: Fix double put in dln2_probe
     - leds: pwm: Don't disable the PWM when the LED should be off
     - leds: trigger: ledtrig-cpu:: Fix 'output may be truncated' issue for 'cpu'
     - tty: tty_jobctrl: fix pid memleak in disassociate_ctty()
     - usb: dwc2: fix possible NULL pointer dereference caused by driver
       concurrency
     - dmaengine: ti: edma: handle irq_of_parse_and_map() errors
     - misc: st_core: Do not call kfree_skb() under spin_lock_irqsave()
     - USB: usbip: fix stub_dev hub disconnect
     - dmaengine: pxa_dma: Remove an erroneous BUG_ON() in pxad_free_desc()
     - f2fs: fix to initialize map.m_pblk in f2fs_precache_extents()
     - modpost: fix tee MODULE_DEVICE_TABLE built on big-endian host
     - [powerpc*] 40x: Remove stale PTE_ATOMIC_UPDATES macro
     - [powerpc*] xive: Fix endian conversion size
     - [powerpc*] imc-pmu: Use the correct spinlock initializer.
     - [powerpc*] pseries: fix potential memory leak in init_cpu_associativity()
     - xhci: Loosen RPM as default policy to cover for AMD xHC 1.1
     - usb: host: xhci-plat: fix possible kernel oops while resuming
     - perf machine: Avoid out of bounds LBR memory read
     - perf hist: Add missing puts to hist__account_cycles
     - i3c: Fix potential refcount leak in i3c_master_register_new_i3c_devs
     - rtc: pcf85363: fix wrong mask/val parameters in regmap_update_bits call
     - pcmcia: cs: fix possible hung task and memory leak pccardd()
     - pcmcia: ds: fix refcount leak in pcmcia_device_add()
     - pcmcia: ds: fix possible name leak in error path in pcmcia_device_add()
     - media: i2c: max9286: Fix some redundant of_node_put() calls
     - media: bttv: fix use after free error due to btv->timeout timer
     - media: s3c-camif: Avoid inappropriate kfree()
     - media: vidtv: psi: Add check for kstrdup
     - media: vidtv: mux: Add check and kfree for kstrdup
     - media: cedrus: Fix clock/reset sequence
     - media: dvb-usb-v2: af9035: fix missing unlock
     - regmap: prevent noinc writes from clobbering cache
     - pwm: sti: Avoid conditional gotos
     - pwm: sti: Reduce number of allocations and drop usage of chip_data
     - pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume
     - Input: synaptics-rmi4 - fix use after free in rmi_unregister_function()
     - llc: verify mac len before reading mac header
     - hsr: Prevent use after free in prp_create_tagged_frame()
     - tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING
     - inet: shrink struct flowi_common
     - dccp: Call security_inet_conn_request() after setting IPv4 addresses.
     - dccp/tcp: Call security_inet_conn_request() after setting IPv6 addresses.
     - net: r8169: Disable multicast filter for RTL8168H and RTL8107E
     - Fix termination state for idr_for_each_entry_ul()
     - net: stmmac: xgmac: Enable support for multiple Flexible PPS outputs
     - net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT
     - net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc
     - net/smc: put sk reference if close work was canceled
     - tg3: power down device only on SYSTEM_POWER_OFF
     - r8169: respect userspace disabling IFF_MULTICAST
     - netfilter: xt_recent: fix (increase) ipv6 literal buffer length
     - netfilter: nft_redir: use `struct nf_nat_range2` throughout and
       deduplicate eval call-backs
     - netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses
     - [x86] Share definition of __is_canonical_address()
     - [x86] sev-es: Allow copy_from_kernel_nofault() in earlier boot
     - drm/syncobj: fix DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE
     - fbdev: imsttfb: Fix error path of imsttfb_probe()
     - fbdev: imsttfb: fix a resource leak in probe
     - fbdev: fsl-diu-fb: mark wr_reg_wa() static
     - tracing/kprobes: Fix the order of argument descriptions
     - Revert "mmc: core: Capture correct oemid-bits for eMMC cards"
     - btrfs: use u64 for buffer sizes in the tree search ioctls
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.202
     - perf/core: Bail out early if the request AUX area is out of bound
     - [armhf] clocksource/drivers/timer-imx-gpt: Fix potential memory leak
     - [x86] mm: Drop the 4 MB restriction on minimal NUMA node memory size
     - wifi: mac80211_hwsim: fix clang-specific fortify warning
     - wifi: mac80211: don't return unset power in ieee80211_get_tx_power()
     - bpf: Detect IP == ksym.end as part of BPF program
     - wifi: ath9k: fix clang-specific fortify warnings
     - wifi: ath10k: fix clang-specific fortify warning
     - net: annotate data-races around sk->sk_tx_queue_mapping
     - net: annotate data-races around sk->sk_dst_pending_confirm
     - wifi: ath10k: Don't touch the CE interrupt registers after power up
     - Bluetooth: btusb: Add date->evt_skb is NULL check
     - Bluetooth: Fix double free in hci_conn_cleanup
     - [x86] platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e
     - [arm64] drm/msm/dp: skip validity check for DP CTS EDID checksum
     - drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7
     - drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga
     - drm/amdgpu: Fix potential null pointer derefernce
     - drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL
     - ASoC: soc-card: Add storage for PCI SSID
     - crypto: pcrypt - Fix hungtask for PADATA_RESET
     - [amd64] RDMA/hfi1: Use FIELD_GET() to extract Link Width
     - fs/jfs: Add check for negative db_l2nbperpage
     - fs/jfs: Add validity check for db_maxag and db_agpref
     - jfs: fix array-index-out-of-bounds in dbFindLeaf
     - jfs: fix array-index-out-of-bounds in diAlloc
     - HID: lenovo: Detect quirk-free fw on cptkbd and stop applying workaround
     - [armel,armhf] 9320/1: fix stack depot IRQ stack filter
     - ALSA: hda: Fix possible null-ptr-deref when assigning a stream
     - atm: iphase: Do PCI error checks on own line
     - scsi: libfc: Fix potential NULL pointer dereference in
       fc_lport_ptp_setup()
     - HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W
     - exfat: support handle zero-size directory
     - usb: gadget: f_ncm: Always set current gadget in ncm_bind()
     - 9p/trans_fd: Annotate data-racy writes to file::f_flags
     - [armhf] i2c: sun6i-p2wi: Prevent potential division by zero
     - media: gspca: cpia1: shift-out-of-bounds in set_flicker
     - media: vivid: avoid integer overflow
     - gfs2: ignore negated quota changes
     - gfs2: fix an oops in gfs2_permission
     - media: imon: fix access to invalid resource for the second interface
     - drm/amd/display: Avoid NULL dereference of timing generator
     - [armhf] ASoC: ti: omap-mcbsp: Fix runtime PM underflow warnings
     - drm/amdgpu: fix software pci_unplug on some chips
     - pwm: Fix double shift bug
     - wifi: iwlwifi: Use FW rate for non-data frames
     - xhci: turn cancelled td cleanup to its own function
     - SUNRPC: ECONNRESET might require a rebind
     - SUNRPC: Add an IS_ERR() check back to where it was
     - NFSv4.1: fix SP4_MACH_CRED protection for pnfs IO
     - SUNRPC: Fix RPC client cleaned up the freed pipefs dentries
     - gfs2: Silence "suspicious RCU usage in gfs2_permission" warning
     - ipvlan: add ipvlan_route_v6_outbound() helper
     - tty: Fix uninit-value access in ppp_sync_receive()
     - [arm64] net: hns3: fix variable may not initialized problem in
       hns3_init_mac_addr()
     - [arm64] net: hns3: fix VF reset fail issue
     - tipc: Fix kernel-infoleak due to uninitialized TLV value
     - ppp: limit MRU to 64K
     - xen/events: fix delayed eoi list handling
     - ptp: annotate data-race around q->head and q->tail
     - bonding: stop the device in bond_setup_by_slave()
     - netfilter: nf_conntrack_bridge: initialize err to 0
     - net: stmmac: fix rx budget limit check
     - net/mlx5e: fix double free of encap_header
     - net/mlx5_core: Clean driver version and name
     - net/mlx5e: Check return value of snprintf writing to fw_version buffer for
       representors
     - macvlan: Don't propagate promisc change to lower dev in passthru
     - cifs: spnego: add ';' in HOST_KEY_LEN
     - cifs: fix check of rc in function generate_smb3signingkey
     - [arm64] media: venus: hfi: add checks to perform sanity on queue pointers
     - [powerpc*] perf: Fix disabling BHRB and instruction sampling
     - bpf: Fix check_stack_write_fixed_off() to correctly spill imm
     - bpf: Fix precision tracking for BPF_ALU | BPF_TO_BE | BPF_END
     - scsi: mpt3sas: Fix loop logic
     - scsi: megaraid_sas: Increase register read retry rount from 3 to 30 for
       selected registers
     - [x86] cpu/hygon: Fix the CPU topology evaluation for real
     - [x86] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
     - [x86] KVM: x86: Ignore MSR_AMD64_TW_CFG access
     - audit: don't take task_lock() in audit_exe_compare() code path
     - audit: don't WARN_ON_ONCE(!current->mm) in audit_exe_compare()
     - tty/sysrq: replace smp_processor_id() with get_cpu()
     - hvc/xen: fix console unplug
     - hvc/xen: fix error path in xen_hvc_init() to always register frontend
       driver
     - PCI/sysfs: Protect driver's D3cold preference from user space
     - watchdog: move softlockup_panic back to early_param
     - ACPI: resource: Do IRQ override on TongFang GMxXGxx
     - [arm64] Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer
     - mmc: vub300: fix an error code
     - mmc: sdhci_am654: fix start loop index for TAP value parsing
     - PCI/ASPM: Fix L1 substate handling in aspm_attr_store_common()
     - [arm64] dts: qcom: ipq6018: Fix hwlock index for SMEM
     - PM: hibernate: Use __get_safe_page() rather than touching the list
     - PM: hibernate: Clean up sync_read handling in snapshot_write_next()
     - rcu: kmemleak: Ignore kmemleak false positives when RCU-freeing objects
     - btrfs: don't arbitrarily slow down delalloc if we're committing
     - [arm64] firmware: qcom_scm: use 64-bit calling convention only when client
       is 64-bit
     - ima: detect changes to the backing overlay file
     - wifi: ath11k: fix temperature event locking
     - wifi: ath11k: fix dfs radar event locking
     - wifi: ath11k: fix htt pktlog locking
     - mmc: meson-gx: Remove setting of CMD_CFG_ERROR
     - genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware
     - jbd2: fix potential data lost in recovering journal raced with
       synchronizing fs bdev
     - quota: explicitly forbid quota files from being encrypted
     - kernel/reboot: emergency_restart: Set correct system_state
     - i2c: core: Run atomic i2c xfer when !preemptible
     - mcb: fix error handling for different scenarios when parsing
     - [armhf] dmaengine: stm32-mdma: correct desc prep when channel running
     - mm/cma: use nth_page() in place of direct struct page manipulation
     - mm/memory_hotplug: use pfn math in place of direct struct page
       manipulation
     - mtd: cfi_cmdset_0001: Byte swap OTP info
     - xhci: Enable RPM on controllers that support low-power states
     - ALSA: info: Fix potential deadlock at disconnection
     - ALSA: hda/realtek - Add Dell ALC295 to pin fall back table
     - ALSA: hda/realtek - Enable internal speaker of ASUS K6500ZC
     - serial: meson: remove redundant initialization of variable id
     - tty: serial: meson: retrieve port FIFO size from DT
     - serial: meson: Use platform_get_irq() to get the interrupt
     - tty: serial: meson: fix hard LOCKUP on crtscts mode
     - cpufreq: stats: Fix buffer overflow detection in trans_stats()
     - Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x0cb8:0xc559
     - bluetooth: Add device 0bda:887b to device tables
     - bluetooth: Add device 13d3:3571 to device tables
     - Bluetooth: btusb: Add RTW8852BE device 13d3:3570 to device tables
     - Bluetooth: btusb: Add 0bda:b85b for Fn-Link RTL8852BE
     - Revert ncsi: Propagate carrier gain/loss events to the NCSI controller
     - lsm: fix default return value for vm_enough_memory
     - lsm: fix default return value for inode_getsecctx
     - i2c: designware: Disable TX_EMPTY irq while waiting for block length byte
     - net: phylink: initialize carrier state at creation
     - i2c: i801: fix potential race in i801_block_transaction_byte_by_byte
     - f2fs: avoid format-overflow warning
     - media: lirc: drop trailing space from scancode transmit
     - media: sharp: fix sharp encoding
     - [arm64] media: venus: hfi_parser: Add check to keep the number of codecs
       within range
     - [arm64] media: venus: hfi: fix the check to handle session buffer
       requirement
     - [arm64] media: venus: hfi: add checks to handle capabilities from firmware
     - nfsd: fix file memleak on client_opens_release
     - mm: kmem: drop __GFP_NOFAIL when allocating objcg vectors
     - Revert "net: r8169: Disable multicast filter for RTL8168H and RTL8107E"
     - ext4: apply umask if ACL support is disabled
     - ext4: correct offset of gdb backup in non meta_bg group to update_backups
     - ext4: correct return value of ext4_convert_meta_bg
     - ext4: correct the start block of counting reserved clusters
     - ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks
     - drm/amd/pm: Handle non-terminated overdrive commands.
     - drm/amdgpu: fix error handling in amdgpu_bo_list_get()
     - drm/amd/display: Change the DMCUB mailbox memory location from FB to inbox
     - io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid
       (CVE-2023-46862)
     - tracing: Have trace_event_file have ref counters
     - netfilter: nftables: update table flags from the commit phase
     - netfilter: nf_tables: fix table flag updates
     - netfilter: nf_tables: disable toggling dormant table state more than once
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.203
     - RDMA/irdma: Prevent zero-length STAG registration (CVE-2023-25775)
     - afs: Fix afs_server_list to be cleaned up with RCU
     - afs: Make error on cell lookup failure consistent with OpenAFS
     - [arm64,armhf] drm/panel: simple: Fix Innolux G101ICE-L01 bus flags
     - [arm64,armhf] drm/panel: simple: Fix Innolux G101ICE-L01 timings
     - wireguard: use DEV_STATS_INC()
     - ata: pata_isapnp: Add missing error check for devm_ioport_map()
     - [arm64,armhf] drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP
       full
     - HID: core: store the unique system identifier in hid_device
     - HID: fix HID device resource race between HID core and debugging support
     - ipv4: Correct/silence an endian warning in __ip_do_redirect
     - net: usb: ax88179_178a: fix failed operations during ax88179_reset
     - net/smc: avoid data corruption caused by decline
     - [armhf] xen: fix xen_vcpu_info allocation alignment
     - [amd64,arm64] amd-xgbe: handle corner-case during sfp hotplug
     - [amd64,arm64] amd-xgbe: handle the corner-case during tx completion
     - [amd64,arm64] amd-xgbe: propagate the correct speed and duplex status
     - afs: Return ENOENT if no cell DNS record can be found
     - afs: Fix file locking on R/O volumes to operate in local mode
     - nvmet: remove unnecessary ctrl parameter
     - nvmet: nul-terminate the NQNs passed in the connect command
       (CVE-2023-6121)
     - [arm64] USB: dwc3: qcom: fix resource leaks on probe deferral
     - [arm64] USB: dwc3: qcom: fix ACPI platform device leak
     - lockdep: Fix block chain corruption
     - ext4: add a new helper to check if es must be kept
     - ext4: factor out __es_alloc_extent() and __es_free_extent()
     - ext4: use pre-allocated es in __es_insert_extent()
     - ext4: use pre-allocated es in __es_remove_extent()
     - ext4: using nofail preallocation in ext4_es_remove_extent()
     - ext4: using nofail preallocation in ext4_es_insert_delayed_block()
     - ext4: using nofail preallocation in ext4_es_insert_extent()
     - ext4: fix slab-use-after-free in ext4_es_insert_extent()
     - ext4: make sure allocate pending entry not fail
     - nfsd: lock_rename() needs both directories to live on the same fs
     - [arm*] ASoC: simple-card: fixup asoc_simple_probe() error handling
     - ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA
     - swiotlb-xen: provide the "max_mapping_size" method
     - bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in
       btree_gc_coalesce()
     - bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race
     - [s390x] dasd: protect device queue against concurrent access
     - USB: serial: option: add Luat Air72*U series products
     - [x86] hv_netvsc: Fix race of register_netdevice_notifier and VF register
     - [x86] hv_netvsc: Mark VF as slave before exposing it to user-mode
     - dm-delay: fix a race between delay_presuspend and delay_bio
     - bcache: check return value from btree_node_alloc_replacement()
     - bcache: prevent potential division by zero error
     - bcache: fixup init dirty data errors
     - bcache: fixup lock c->root error
     - USB: serial: option: add Fibocom L7xx modules
     - USB: serial: option: fix FM101R-GL defines
     - USB: serial: option: don't claim interface 4 for ZTE MF290
     - [arm*] USB: dwc2: write HCINT with INTMASK applied
     - [arm64,armhf] usb: dwc3: Fix default mode initialization
     - [arm64,armhf] usb: dwc3: set the dma max_seg_size
     - [arm64,armhf] USB: dwc3: qcom: fix wakeup after probe deferral
     - io_uring: fix off-by one bvec index
     - pinctrl: avoid reload of p state in list iteration
     - firewire: core: fix possible memory leak in create_units()
     - mmc: block: Do not lose cache flush during CQE error recovery
     - ALSA: hda: Disable power-save on KONTRON SinglePC
     - ALSA: hda/realtek: Headset Mic VREF to 100%
     - ALSA: hda/realtek: Add supported ALC257 for ChromeOS
     - dm-verity: align struct dm_verity_fec_io properly
     - dm verity: don't perform FEC for failed readahead IO
     - bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
     - [amd64] iommu/vt-d: Add MTL to quirk list to skip TE disabling
     - [powerpc*] Don't clobber f0/vs0 during fp|altivec register save
       (Closes: #1032104)
     - btrfs: add dmesg output for first mount and last unmount of a filesystem
     - btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
     - btrfs: fix off-by-one when checking chunk map includes logical address
     - btrfs: send: ensure send_fd is writable
     - btrfs: make error messages more clear when getting a chunk map
     - Input: xpad - add HyperX Clutch Gladiate Support
     - [x86] hv_netvsc: fix race of netvsc and VF register_netdevice
     - USB: core: Change configuration warnings to notices
     - usb: config: fix iteration issue in 'usb_get_bos_descriptor()'
     - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet
       (CVE-2023-6932)
     - [arm64] dpaa2-eth: increase the needed headroom to account for alignment
     - net: stmmac: xgmac: Disable FPE MMC interrupts
     - Revert "workqueue: remove unused cancel_work()"
     - r8169: prevent potential deadlock in rtl8169_close
     - smb3: fix touch -h of symlink
     - [x86] ASoC: Intel: Move soc_intel_is_foo() helpers to a generic header
     - [x86] ASoC: SOF: sof-pci-dev: use community key on all Up boards
     - [x86] ASoC: SOF: sof-pci-dev: add parameter to override topology filename
     - [x86] ASoC: SOF: sof-pci-dev: don't use the community key on APL
       Chromebooks
     - [x86] ASoC: SOF: sof-pci-dev: Fix community key quirk detection
     - [s390x] mm: fix phys vs virt confusion in mark_kernel_pXd() functions
       family
     - [s390x] cmma: fix detection of DAT pages
     - ima: annotate iint mutex to avoid lockdep false positive warnings
     - driver core: Move the "removable" attribute from USB to core
     - drm/amdgpu: don't use ATRM for external devices
     - fs: add ctime accessors infrastructure
     - smb3: fix caching of ctime on setxattr
     - scsi: core: Introduce the scsi_cmd_to_rq() function
     - scsi: qla2xxx: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
     - scsi: qla2xxx: Fix system crash due to bad pointer access
     - [armhf] cpufreq: imx6q: don't warn for disabling a non-existing frequency
     - [armhf] cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily
     - mmc: cqhci: Increase recovery halt timeout
     - mmc: cqhci: Warn of halt or task clear failure
     - mmc: cqhci: Fix task clearing in CQE error recovery
     - mmc: core: convert comma to semicolon
     - mmc: block: Retry commands in CQE error recovery
     - mmc: core: add helpers mmc_regulator_enable/disable_vqmmc
     - r8169: disable ASPM in case of tx timeout
     - r8169: fix deadlock on RTL8125 in jumbo mtu mode
     - driver core: Release all resources during unbind before updating device
       links
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.204
     - hrtimers: Push pending hrtimers away from outgoing CPU earlier
     - i2c: designware: Fix corrupted memory seen in the ISR
     - netfilter: ipset: fix race condition between swap/destroy and kernel side
       add/del/test
     - tg3: Move the [rt]x_dropped counters to tg3_napi
     - tg3: Increment tx_dropped in tg3_tso_bug()
     - kconfig: fix memory leak from range properties
     - drm/amdgpu: correct chunk_ptr to a pointer to chunk.
     - [x86] platform/x86: asus-wmi: Add support for SW_TABLET_MODE on UX360
     - [x86] platform/x86: asus-nb-wmi: Allow configuring SW_TABLET_MODE method
       with a module option
     - [x86] platform/x86: asus-nb-wmi: Add tablet_mode_sw=lid-flip quirk for the
       TP200s
     - [x86] asus-wmi: Add dgpu disable method
     - [x86] platform/x86: asus-wmi: Adjust tablet/lidflip handling to use enum
     - [x86] platform/x86: asus-wmi: Add support for ROG X13 tablet mode
     - [x86] platform/x86: asus-wmi: Simplify tablet-mode-switch probing
     - [x86] platform/x86: asus-wmi: Simplify tablet-mode-switch handling
     - [x86] platform/x86: asus-wmi: Move i8042 filter install to shared asus-wmi
       code
     - of: base: Fix some formatting issues and provide missing descriptions
     - of: Fix kerneldoc output formatting
     - of: Add missing 'Return' section in kerneldoc comments
     - of: dynamic: Fix of_reconfig_get_state_change() return value documentation
     - ipv6: fix potential NULL deref in fib6_add()
     - hv_netvsc: rndis_filter needs to select NLS
     - net: arcnet: com20020 fix error handling
     - arcnet: restoring support for multiple Sohard Arcnet cards
     - i40e: Fix unexpected MFS warning message
     - net: bnxt: fix a potential use-after-free in bnxt_init_tc
     - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit()
     - [arm64] net: hns: fix fake link up on xge port
     - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket
     - tcp: do not accept ACK of bytes we never sent
     - bpf: sockmap, updating the sg structure should also update curr
     - [arm64] tee: optee: Fix supplicant based device enumeration
     - RDMA/bnxt_re: Correct module description string
     - [x86] hwmon: (acpi_power_meter) Fix 4.29 MW bug
     - tracing: Fix a warning when allocating buffered events fails
     - scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle()
     - [armhf] imx: Check return value of devm_kasprintf in imx_mmdc_perf_init
     - ALSA: pcm: fix out-of-bounds in snd_pcm_state_names
     - ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5
     - nilfs2: fix missing error check for sb_set_blocksize call
     - nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()
     - checkstack: fix printed address
     - tracing: Always update snapshot buffer size
     - tracing: Disable snapshot buffer when stopping instance tracers
     - tracing: Fix incomplete locking when disabling buffered events
     - tracing: Fix a possible race when disabling buffered events
     - packet: Move reference count in packet_sock to atomic_long_t
     - [x86] misc: mei: client.c: return negative error code in mei_cl_write
     - [x86] misc: mei: client.c: fix problem of return '-EOVERFLOW' in
       mei_cl_write
     - ring-buffer: Force absolute timestamp on discard of event
     - tracing: Set actual size after ring buffer resize
     - tracing: Stop current tracer when resizing buffer
     - perf/core: Add a new read format to get a number of lost samples
     - perf: Fix perf_event_validate_size() (CVE-2023-6931)
     - gpiolib: sysfs: Fix error handling on failed export
     - drm/amdgpu: correct the amdgpu runtime dereference usage count
     - usb: gadget: f_hid: fix report descriptor allocation
     - parport: Add support for Brainboxes IX/UC/PX parallel cards
     - Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
     - usb: typec: class: fix typec_altmode_put_partner to put plugs
     - [arm*] PL011: Fix DMA support
     - [x86] CPU/AMD: Check vendor in the AMD microcode callback
     - [s390x] KVM: s390/mm: Properly reset no-dat
     - [mips*] Loongson64: Reserve vgabios memory on boot
     - [mips*] Loongson64: Enable DMA noncoherent support
     - io_uring/af_unix: disable sending io_uring over sockets (CVE-2023-6531)
     - netlink: don't call ->netlink_bind with table lock held
     - genetlink: add CAP_NET_ADMIN test for multicast bind
     - psample: Require 'CAP_NET_ADMIN' when joining "packets" group
     - drop_monitor: Require 'CAP_SYS_ADMIN' when joining "events" group
     - netfilter: nft_set_pipapo: skip inactive elements during set walk
       (CVE-2023-6817)
     - [x86] platform/x86: asus-wmi: Fix kbd_dock_devid tablet-switch reporting
     - [x86] platform/x86: asus-wmi: Document the dgpu_disable sysfs attribute
     - mmc: block: Be sure to wait while busy in CQE error recovery
     - Revert "btrfs: add dmesg output for first mount and last unmount of a
       filesystem"
     - cifs: Fix non-availability of dedup breaking generic/304
     - smb: client: fix potential NULL deref in parse_dfs_referrals()
     - devcoredump : Serialize devcd_del work
     - devcoredump: Send uevent once devcd is ready
     - r8169: fix rtl8125b PAUSE frames blasting when suspended
     https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.205
     - netfilter: nf_tables: fix 'exist' matching on bigendian arches
     - afs: Fix refcount underflow from error handling race (Closes: #1052304)
     - HID: lenovo: Restrict detection of patched firmware only to USB cptkbd
     - net: ipv6: support reporting otherwise unknown prefix flags in
       RTM_NEWPREFIX
     - atm: solos-pci: Fix potential deadlock on &cli_queue_lock
     - atm: solos-pci: Fix potential deadlock on &tx_queue_lock
     - net: vlan: introduce skb_vlan_eth_hdr()
     - net: fec: correct queue selection
     - atm: Fix Use-After-Free in do_vcc_ioctl (CVE-2023-51780)
     - net/rose: Fix Use-After-Free in rose_ioctl (CVE-2023-51782)
     - qed: Fix a potential use-after-free in qed_cxt_tables_alloc
     - net: Remove acked SYN flag from packet in the transmit queue correctly
     - net: ena: Destroy correct number of xdp queues upon failure
     - net: ena: Fix XDP redirection error
     - sign-file: Fix incorrect return values check
     - vsock/virtio: Fix unsigned integer wrap around in
       virtio_transport_has_space()
     - net: stmmac: use dev_err_probe() for reporting mdio bus registration
       failure
     - net: stmmac: Handle disabled MDIO busses from devicetree
     - appletalk: Fix Use-After-Free in atalk_ioctl (CVE-2023-51781)
     - net: atlantic: fix double free in ring reinit logic
     - cred: switch to using atomic_long_t
     - fuse: dax: set fc->dax to NULL in fuse_dax_conn_free()
     - ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants
     - ALSA: hda/realtek: Apply mute LED quirk for HP15-db
     - Revert "PCI: acpiphp: Reassign resources on bridge if necessary"
     - PCI: loongson: Limit MRRS to 256 (Closes: #1035587)
     - usb: aqc111: check packet for fixup for true limit
     - blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock
       required!"
     - bcache: avoid oversize memory allocation by small stripe_size
     - bcache: remove redundant assignment to variable cur_idx
     - bcache: add code comments for bch_btree_node_get() and
       __bch_btree_node_alloc()
     - bcache: avoid NULL checking to c->root in run_cache_set()
     - [x86] platform/x86: intel_telemetry: Fix kernel doc descriptions
     - HID: glorious: fix Glorious Model I HID report
     - HID: add ALWAYS_POLL quirk for Apple kb
     - HID: hid-asus: reset the backlight brightness level on resume
     - HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad
     - asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation
     - net: usb: qmi_wwan: claim interface 4 for ZTE MF290
     - HID: hid-asus: add const to read-only outgoing usb buffer
     - perf: Fix perf_event_validate_size() lockdep splat
     - soundwire: stream: fix NULL pointer dereference for multi_link
     - ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS
     - [arm64] mm: Always make sw-dirty PTEs hw-dirty in pte_modify
     - team: Fix use-after-free when an option instance allocation fails
     - ring-buffer: Fix memory leak of free page
     - tracing: Update snapshot buffer on resize if it is allocated
     - ring-buffer: Have saved event hold the entire event
     - ring-buffer: Fix writing to the buffer with max_data_size
     - ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs
     - USB: gadget: core: adjust uevent timing on gadget unbind
     - tty: n_gsm: fix tty registration before control channel open
     - tty: n_gsm, remove duplicates of parameters
     - tty: n_gsm: add sanity check for gsm->receive in gsm_receive_buf()
     - [powerpc*] ftrace: Create a dummy stackframe to fix stack unwind
     - [powerpc*] ftrace: Fix stack teardown in ftrace_no_trace
 .
   [ Salvatore Bonaccorso ]
   * Bump ABI to 27
   * [rt] Refresh "net: Properly annotate the try-lock for the seqlock"
     Adapt to changes from upstream a8dd21118b0f ("seqlock: Prefix internal
     seqcount_t-only macros with a "do_"") in 5.10.198.
   * Refresh "arm64: compat: Implement misalignment fixups for multiword loads"
   * Do not enable DEBUG_PREEMPT (not enabled by default since 5.10.199)
   * [rt] Update to 5.10.201-rt98
   * [rt] Update to 5.10.204-rt100
   * [arm64] drivers/vfio: Don't enable VFIO_NOIOMMU.
     This is a breach of the integrity lockdown requirement of secure boot
     and thus cannot be enabled.
     Thanks to Bastian Blank and Ben Hutchings
   * netfilter: nf_tables: skip set commit for deleted/destroyed sets
Checksums-Sha1:
 e634b8ce79684f8b6e2e4aee29f041f699f6dd25 205890 linux_5.10.205-1.dsc
 1b02cbaa07c770056247920ee3c9796f67b3edd1 121904328 linux_5.10.205.orig.tar.xz
 1f5cb503c6a92ddd096d6d5d823073d6f5ffe76d 1644312 linux_5.10.205-1.debian.tar.xz
 73610e40936ad2dbe5948ca2676f40c184e40f9c 7009 linux_5.10.205-1_source.buildinfo
Checksums-Sha256:
 6e941d3f6e372c75e57adcadfe91d4d4a59046fe767b8f9308104a35ed7b561a 205890 linux_5.10.205-1.dsc
 878658989952ffdc22928faf15dfa6c66ea9a5e49b412e5ba3bc16784ae1f1b6 121904328 linux_5.10.205.orig.tar.xz
 f5dd034a5847a0a1e67cd9607fd89e642b3088a6779b705c2abb764d05ae8975 1644312 linux_5.10.205-1.debian.tar.xz
 e981444539aeef6d8388a4ba087d6141c95ca1f95da69fe9051eb582be6ff554 7009 linux_5.10.205-1_source.buildinfo
Files:
 38c1ad229a162e7c1c8807af759e492c 205890 kernel optional linux_5.10.205-1.dsc
 96e130d88a20da49d9668454fe5bda83 121904328 kernel optional linux_5.10.205.orig.tar.xz
 b042fa2c3770de666d55b22f9070a53a 1644312 kernel optional linux_5.10.205-1.debian.tar.xz
 8b94dfc935fe7acdeb780c8af784bdfa 7009 kernel optional linux_5.10.205-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmWP5ipfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EHBYQAIVAqUWk/xd6TsU75dBrLJGKrDAYJ21g
wyfbJDsZdPJ/oXXd7Vwue3T/ptZ6IG/whhd8806ElO7zRs8tDq59pVVafqLwehkb
LZRlM0zAmvlYKdvXYn/YjKKTmPBx4uNsiv3EerGkaXo9KfbdozH5Ya6Ytt1psbzN
XrS7End0BiAekWjkOepTkAnpcs0TObsZZnRduHtd6O/7PybeyFbTugy2lPXsivql
8LlKhUb77416P7aQd9ESNlHuP+9wR9N25zbEAI1l8deTzeP04NTZAQQfMqpyv/XV
zenCSZAF85nKs3BVXUg4fxwH8IJHpqu1JBZW1SWpwVJW2+1nJvPlJH1A4uFklNE1
DLGbrWdKHW1DFzaBW7Gke/E63oDRsIEomD5g2oY3+a2dXenr8PLG2G/aS95VpNKl
Sb5iKtrgL93asUoY/7ASKwU7I3n5jIcof36ZGyPPXRbzzX0KCzxkI1UByFOT1AZH
KtGeXu3K6R5IE/2cQcKBrbFthqBXNd0jcqe5m21vO97GYFAY97nlYduhUvzEaL/9
QFXeXFYCmcDGVsEIttBM/A18uRStkCsavOO47QXLKwLjhIYFBBS4BVr490vNjTl4
2PFuZXaQcDCikRyiVvQlIULYhq2+KUdPIzkVXLQJ+VKeea9t2BcxUhj1x+evL9bD
8j6Q7c/6qD1Q
=f5Id
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.