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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 12 May 2007 05:01:17 +0400
From:	Oleg Nesterov <>
To:	Linus Torvalds <>
Cc:	"Rafael J. Wysocki" <>,
	Andrew Morton <>,
	Gautham R Shenoy <>,
	LKML <>, Pavel Machek <>,
	"Eric W. Biederman" <>
Subject: Re: [PATCH 1/7] Freezer: Read PF_BORROWED_MM in a nonracy way

On 05/12, Oleg Nesterov wrote:
> Do we need freezer? Should we freeze kernel threads? I can't judge. I tried
> to read a long thread about suspend, and failed to understand it.
> I personally think we can simplify things if CPU-hotplug use freezer, at least.

Just a small example,


		 * Kernel threads bound to a single CPU can safely use
		 * smp_processor_id():
		this_mask = cpumask_of_cpu(this_cpu);

		if (cpus_equal(current->cpus_allowed, this_mask))
			goto out;

This is not true with CONFIG_HOTPLUG_CPU. This becomes true if we freeze
the kernel threads from CPU_DOWN_PREPARE to CPU_DEAD.


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