public inbox for [email protected]
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <[email protected]>
To: Pavel Begunkov <[email protected]>
Cc: Xan Charbonnet <[email protected]>,
	[email protected], Jens Axboe <[email protected]>,
	Bernhard Schmidt <[email protected]>,
	[email protected], [email protected]
Subject: Re: Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs
Date: Fri, 24 Jan 2025 06:24:55 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

HI Pavel, hi Jens,

On Thu, Jan 23, 2025 at 11:20:40PM +0000, Pavel Begunkov wrote:
> On 1/23/25 20:49, Salvatore Bonaccorso wrote:
> > Hi Xan,
> > 
> > On Thu, Jan 23, 2025 at 02:31:34PM -0600, Xan Charbonnet wrote:
> > > I rented a Linode and have been trying to load it down with sysbench
> > > activity while doing a mariabackup and a mysqldump, also while spinning up
> > > the CPU with zstd benchmarks.  So far I've had no luck triggering the fault.
> > > 
> > > I've also been doing some kernel compilation.  I followed this guide:
> > > https://www.dwarmstrong.org/kernel/
> > > (except that I used make -j24 to build in parallel and used make
> > > localmodconfig to compile only the modules I need)
> > > 
> > > I've built the following kernels:
> > > 6.1.123 (equivalent to linux-image-6.1.0-29-amd64)
> > > 6.1.122
> > > 6.1.121
> > > 6.1.120
> > > 
> > > So far they have all exhibited the behavior.  Next up is 6.1.119 which is
> > > equivalent to linux-image-6.1.0-28-amd64.  My expectation is that the fault
> > > will not appear for this kernel.
> > > 
> > > It looks like the issue is here somewhere:
> > > https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.120
> > > 
> > > I have to work on some other things, and it'll take a while to prove the
> > > negative (that is, to know that the failure isn't happening).  I'll post
> > > back with the 6.1.119 results when I have them.
> > 
> > Additionally please try with 6.1.120 and revert this commit
> > 
> > 3ab9326f93ec ("io_uring: wake up optimisations")
> > 
> > (which landed in 6.1.120).
> > 
> > If that solves the problem maybe we miss some prequisites in the 6.1.y
> > series here?
> 
> I'm not sure why the commit was backported (need to look it up),
> but from a quick look it does seem to miss a barrier present in
> the original patch.

Ack, this was here for reference:
https://lore.kernel.org/stable/[email protected]/

Xan Charbonnet was able to confirm in https://bugs.debian.org/1093243#99 that
indeed reverting the commit fixes the mariadb related hangs.

Regards,
Salvatore

  parent reply	other threads:[~2025-01-24  5:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173706089225.4380.9492796104667651797.reportbug@backup22.biblionix.com>
     [not found] ` <[email protected]>
     [not found]   ` <[email protected]>
     [not found]     ` <[email protected]>
2025-01-23 20:05       ` Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs Salvatore Bonaccorso
2025-01-23 20:26         ` Jens Axboe
     [not found] ` <[email protected]>
2025-01-23 20:49   ` Salvatore Bonaccorso
2025-01-23 23:20     ` Pavel Begunkov
2025-01-24  2:10       ` Xan Charbonnet
2025-01-24  5:24       ` Salvatore Bonaccorso [this message]
2025-01-24 10:33         ` Pavel Begunkov
2025-01-24 16:30           ` Xan Charbonnet
2025-01-24 18:40             ` Pavel Begunkov
2025-01-24 20:33               ` Salvatore Bonaccorso
2025-01-24 20:51                 ` Jens Axboe
2025-01-26 22:48                   ` Xan Charbonnet
2025-01-27 16:38                     ` Xan Charbonnet
2025-01-27 17:21                       ` Pavel Begunkov
2025-01-27 16:49                     ` Pavel Begunkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox