mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Pavel Machek <pavel@suse.cz>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] move do_suspend_lowlevel to correct segment
Date: Fri, 16 Jun 2006 08:52:19 +0800	[thread overview]
Message-ID: <1150419139.21189.21.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20060615091934.GG9423@elf.ucw.cz>

Hi Pavel,
On Thu, 2006-06-15 at 11:19 +0200, Pavel Machek wrote:
> > Move do_suspend_lowlevel to correct segment. If it is in the same hugepage
> > with ro data, mark_rodata_ro will make it unexecutable.
> 
> I guess I do not know enough about segments... Original code puts
> saved_magic into .data (and probably puts save_registers there by
> mistake, too -- so you are fixing things), but you put saved_magic
> code into .data, too, so how does its read-only status change?
No, mark_rodata_ro will call change_page_attr, which will split huge
page into small pages, and changes the attr of the pages to PAGE_KERNEL.
mark_rodata_ro just changes rodata to read-only page attr.

> Does x86-64 need similar fix?
It appears not needed

Thanks,
Shaohua
> 
> 
> > Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> > ---
> > 
> >  linux-2.6.17-rc5-root/arch/i386/kernel/acpi/wakeup.S |    9 ++++-----
> >  1 files changed, 4 insertions(+), 5 deletions(-)
> > 
> > diff -puN arch/i386/kernel/acpi/wakeup.S~wakeup arch/i386/kernel/acpi/wakeup.S
> > --- linux-2.6.17-rc5/arch/i386/kernel/acpi/wakeup.S~wakeup	2006-06-14 09:21:26.000000000 +0800
> > +++ linux-2.6.17-rc5-root/arch/i386/kernel/acpi/wakeup.S	2006-06-14 09:21:57.000000000 +0800
> > @@ -265,11 +265,6 @@ ENTRY(acpi_copy_wakeup_routine)
> >  	movl	$0x12345678, saved_magic
> >  	ret
> >  
> > -.data
> > -ALIGN
> > -ENTRY(saved_magic)	.long	0
> > -ENTRY(saved_eip)	.long	0
> > -
> >  save_registers:
> >  	leal	4(%esp), %eax
> >  	movl	%eax, saved_context_esp
> > @@ -304,7 +299,11 @@ ret_point:
> >  	call	restore_processor_state
> >  	ret
> >  
> > +.data
> >  ALIGN
> > +ENTRY(saved_magic)	.long	0
> > +ENTRY(saved_eip)	.long	0
> > +
> >  # saved registers
> >  saved_gdt:	.long	0,0
> >  saved_idt:	.long	0,0
> > _
> 
-- 
Shaohua Li <shaohua.li@intel.com>

      reply	other threads:[~2006-06-16  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15  3:39 Shaohua Li
2006-06-15  9:19 ` Pavel Machek
2006-06-16  0:52   ` Shaohua Li [this message]

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=1150419139.21189.21.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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®