linux-kernel - Re: [PATCH] mm/hotplug, x86: Disable ARCH_MEMORY

lists.openwall.net		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 linux-cve-announce 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:	Thu, 18 Jul 2013 11:34:30 -0700
From:	Dave Hansen <dave@...1.net>
To:	Toshi Kani <toshi.kani@...com>
CC:	Dave Hansen <dave.hansen@...el.com>, akpm@...ux-foundation.org,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org, x86@...nel.org,
	isimatu.yasuaki@...fujitsu.com, tangchen@...fujitsu.com,
	vasilis.liaskovitis@...fitbricks.com
Subject: Re: [PATCH] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default

On 07/18/2013 09:26 AM, Toshi Kani wrote:
> On Thu, 2013-07-18 at 08:27 -0700, Dave Hansen wrote:
>> I'd really prefer you don't do this.  Do you really have random
>> processes on your system poking at random sysfs files and then
>> complaining when things break?
> 
> I am afraid that the "probe" interface does not provide the level of
> quality suitable for regular users.  It takes any value and blindly
> extends the page table.

That's like saying that /dev/sda takes any value and blindly writes it
to the disk.

> Also, we are not aware of the use of this
> interface on x86.  Would you elaborate why you need this interface on
> x86?  Is it for your testing, or is it necessary for end-users?  If the
> former, can you modify .config file to enable it?

For me, it's testing.  It allows testing of the memory hotplug software
stack without actual hardware, which is incredibly valuable.  That
includes testing on distribution kernels which I do not want to modify.
 I thought there were some hypervisor users which don't use ACPI for
hotplug event notifications too.

All that I'm asking is that you either leave it the way it is, or make a
Kconfig menu entry for it.

But, really, what's the problem that you're solving?  Has this caused
you issues somehow?  It's been there for, what, 10 years?  Surely it's
part of the ABI.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/