lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Jul 2014 18:00:47 -0400
From:	Sasha Levin <>
To:	Andrew Morton <>,
	Christoph Lameter <>
CC:	Gilad Ben-Yossef <>,
	Thomas Gleixner <>,
	Tejun Heo <>, John Stultz <>,
	Mike Frysinger <>,
	Minchan Kim <>,
	Hakan Akkan <>,
	Max Krasnyansky <>,
	Frederic Weisbecker <>,
	"Paul E. McKenney" <>,,,,,,,
Subject: Re: vmstat: On demand vmstat workers V8

On 07/28/2014 05:54 PM, Andrew Morton wrote:
> Also, Sasha's report showed this:
> [  490.464613] kernel BUG at mm/vmstat.c:1278!
> That's your VM_BUG_ON() in vmstat_update().  That ain't no false
> positive!
> Is this code expecting that schedule_delayed_work() will schedule the
> work on the current CPU?  I don't think it will do that.  Maybe you
> should be looking at schedule_delayed_work_on().

I suspected that the re-queue might be wrong (schedule_delayed_work vs
schedule_delayed_work_on) and tried fixing that, but that didn't solve
the issue.

I could give it another go unless someone sees the issue, I might have
messed something up.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists