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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 8 Feb 2014 18:39:12 -0500
From:	Richard Yao <>
To:	Linus Torvalds <>
Cc:	Mel Gorman <>,
	Andrew Morton <>,
	Rik van Riel <>,
	Eric Van Hensbergen <>,
	Ron Minnich <>,
	Latchesar Ionkov <>,
	"David S. Miller" <>,
	V9FS Develooper Mailing List 
	Linux Netdev Mailing List <>,
	Linux Kernel Mailing List <>,
	"Aneesh Kumar K.V" <>,
	Will Deacon <>,
	Christopher Covington <>,
	Matthew Thode <>
Subject: Re: [PATCH 1/2] mm/vmalloc: export is_vmalloc_or_module_addr

On Feb 8, 2014, at 5:24 PM, Linus Torvalds <> wrote:

> On Sat, Feb 8, 2014 at 12:44 PM, Richard Yao <> wrote:
>> However, is_vmalloc_addr() only applies to the vmalloc region. While all
>> architectures load kernel modules into virtual memory (to my knowledge),
>> some architectures do not load them into the vmalloc region.
> So?
> People shouldn't do IO to module data, so who cares if something is a
> module address or not?
> The thing is, even module *loading* doesn't do IO to the magic module
> addresses - it loads the module data into regular vmalloc space, and
> then copies it into the final location separately.
> And no module should ever do any IO on random static data (and
> certainly not on code).
> So there is _zero_ reason for a driver or a filesystem to use
> is_vmalloc_or_module_addr(). It's just not a valid question to ask.
> If somebody uses module data/code addresses, we're *better* off with a
> oops or other nasty behavior than to try to make it "work".
>            Linus

I will modify this to use is_vmalloc_addr() and send it back to the appropriate subsystem maintainer(s). Thank-you for taking the time to write that explanation.--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists