All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Borislav Petkov <bp@alien8.de>, koichiro.den@canonical.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Koichiro Den <koichiro.den@canonical.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable@vger.kernel.org
Subject: Re: Linux 6.13-rc6
Date: Mon, 6 Jan 2025 05:56:13 -0800	[thread overview]
Message-ID: <20250106-original-opal-shrew-4ecbf0@leitao> (raw)
In-Reply-To: <20250106131817.GAZ3vYGVr3-hWFFPLj@fat_crate.local>

On Mon, Jan 06, 2025 at 02:18:17PM +0100, Borislav Petkov wrote:
> On Sun, Jan 05, 2025 at 02:20:54PM -0800, Linus Torvalds wrote:
> > So we had a slight pickup in commits this last week, but as expected
> > and hoped for, things were still pretty quiet. About twice as many
> > commits as the holiday week, but that's still not all that many.
> > 
> > I expect things will start becoming more normal now that people are
> > back from the holidays and are starting to recover and wake up from
> > their food comas.
> > 
> > In the meantime, below is the shortlog for the last week. Nothing
> > particularly stands out, the changes are dominated by various driver
> > updates (gpu, rdma and networking), with a random smattering of fixes
> > elsewhere.
> 
> Something not well baked managed to sneak in and it is tagged for stable:
> 
> adcfb264c3ed ("vmstat: disable vmstat_work on vmstat_cpu_down_prep()")

Thanks for bissecting it.

I've just confirmed that reverting adcfb264c3ed ("vmstat: disable
vmstat_work on vmstat_cpu_down_prep()") gets rid of the "workqueue: work
disable count underflow" WARNING.

  parent reply	other threads:[~2025-01-06 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 22:20 Linux 6.13-rc6 Linus Torvalds
2025-01-06 13:18 ` Borislav Petkov
2025-01-06 13:33   ` Greg KH
2025-01-06 13:56   ` Breno Leitao [this message]
2025-01-06 14:07   ` Alexander Gordeev
2025-01-06 14:21   ` Koichiro Den
2025-01-07  2:28     ` Andrew Morton
2025-01-07  7:23       ` Borislav Petkov

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 \
    --in-reply-to=20250106-original-opal-shrew-4ecbf0@leitao \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=koichiro.den@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.