Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #78550 > unrolled thread

Bug#1032104: linux: ppc64el iouring corrupted read

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1032104: linux: ppc64el iouring corrupted read Salvatore Bonaccorso <carnil@debian.org> - 2023-03-19 17:10 +0100
    Bug#1032104: linux: ppc64el iouring corrupted read Salvatore Bonaccorso <carnil@debian.org> - 2023-04-06 22:10 +0200

#78550 — Bug#1032104: linux: ppc64el iouring corrupted read

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

[toc] | [next] | [standalone]

#78706

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web