From: Roland McGrath <roland@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Jan Beulich <jbeulich@novell.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
virtualization@lists.osdl.org, Andi Kleen <ak@suse.de>,
lkml <linux-kernel@vger.kernel.org>,
Zachary Amsden <zach@vmware.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO
Date: Thu, 5 Apr 2007 01:58:40 -0700 (PDT) [thread overview]
Message-ID: <20070405085840.2AFD8180055@magilla.sf.frob.com> (raw)
In-Reply-To: Jeremy Fitzhardinge's message of Thursday, 5 April 2007 01:18:35 -0700 <4614B0DB.7040003@goop.org>
Don't change sh_addr in sections with (sh_flags & SHF_ALLOC) == 0. Also,
I'd concur with Jan's suggestion about paranoia warnings for unexpected
DT_* types (and for unexpected st_shndx >= SHN_LORESERVE).
Otherwise, looks ok to me.
Thanks,
Roland
next prev parent reply other threads:[~2007-04-05 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 4:58 [patch 0/2] Updates to compat VDSOs Jeremy Fitzhardinge
2007-04-05 4:58 ` [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO Jeremy Fitzhardinge
2007-04-05 6:31 ` Roland McGrath
2007-04-05 6:46 ` Jeremy Fitzhardinge
2007-04-05 8:14 ` Roland McGrath
2007-04-05 7:10 ` Jan Beulich
2007-04-05 7:31 ` Jeremy Fitzhardinge
2007-04-05 7:45 ` Raharjo, Cahyo (cahr)
2007-04-05 7:47 ` Jan Beulich
2007-04-05 8:14 ` Roland McGrath
2007-04-05 8:18 ` Jeremy Fitzhardinge
2007-04-05 8:54 ` Jan Beulich
2007-04-05 8:58 ` Roland McGrath [this message]
2007-04-05 4:58 ` [patch 2/2] Make COMPAT_VDSO runtime selectable Jeremy Fitzhardinge
2007-04-05 15:53 [patch 0/2] Updates to compat VDSOs Jeremy Fitzhardinge
2007-04-05 15:53 ` [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO Jeremy Fitzhardinge
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=20070405085840.2AFD8180055@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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®