From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: stern@rowland.harvard.edu, sekharan@us.ibm.com, akpm@osdl.org,
linux-kernel@vger.kernel.org, herbert@13thfloor.at,
linux-xfs@oss.sgi.com, xfs-masters@oss.sgi.com
Subject: Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
Date: Tue, 25 Apr 2006 13:54:36 -0700 [thread overview]
Message-ID: <20060425135436.5f4c51fd.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604251336090.3701@g5.osdl.org>
On Tue, 25 Apr 2006 13:38:22 -0700 (PDT) Linus Torvalds wrote:
>
>
> On Tue, 25 Apr 2006, Alan Stern wrote:
> >
> > What about loadable modules? Is their code never loaded into memory that
> > used to be part of an init section?
>
> Their code might _physically_ reside in a re-allocation of an init
> section, but will have a virtual address far away (and it would be the
> virtual address that you'd see if you took the address of a function).
and the freed init data area is poisoned (in 386, x86_64, powerpc, and
sparc64).
---
~Randy
next prev parent reply other threads:[~2006-04-25 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 2:35 [PATCH 0/3] Fix for the bug reported by Herbert on 2.6.17-rc2 sekharan
2006-04-25 2:35 ` [PATCH 1/3] Remove __devinitdata from notifier block definitions sekharan
2006-04-25 2:35 ` [PATCH 2/3] Remove __devinit and __cpuinit from notifier_call definitions sekharan
2006-04-25 2:35 ` [PATCH 3/3] Assert notifier_block and notifier_call are not in init section sekharan
2006-04-25 2:47 ` Linus Torvalds
2006-04-25 2:50 ` Linus Torvalds
2006-04-25 19:01 ` Chandra Seetharaman
2006-04-25 19:16 ` Linus Torvalds
2006-04-25 20:26 ` Alan Stern
2006-04-25 20:38 ` Linus Torvalds
2006-04-25 20:54 ` Randy.Dunlap [this message]
2006-04-25 22:33 ` Chandra Seetharaman
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=20060425135436.5f4c51fd.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sekharan@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.org \
--cc=xfs-masters@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®