From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Justin Madru <jdm64@gawab.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
Jesper Juhl <jj@chaosbits.net>,
lkml <linux-kernel@vger.kernel.org>,
John Stoffel <john@stoffel.org>,
Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [bisected] 2.6.29-rc1 Firefox crashing on page load
Date: Tue, 20 Jan 2009 08:15:56 +0100 [thread overview]
Message-ID: <20090120071555.GA6165@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <49751BA0.1040004@gawab.com>
On Mon, Jan 19, 2009 at 04:32:32PM -0800, Justin Madru wrote:
> Justin P. Mattock wrote:
>> Justin Madru wrote:
> Ok, finally bisected the bug, but the commit isn't related to networking!
> I did: git revert 4217458dafaa57d8e26a46f5d05ab8c53cf64191
> commit 4217458dafaa57d8e26a46f5d05ab8c53cf64191
> Author: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> Date: Fri Dec 5 17:17:09 2008 -0800
>
> x86: signal: change type of paramter for sys_rt_sigreturn()
>
> Impact: cleanup on 32-bit
>
> Peter pointed this parameter can be changed.
>
> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> :040000 040000 f5fba48247ff200092c38a54e334f495917229d5
> b901159897e5d85e0dc2a0c9d904d9a73c1d58a2 M arch
>
> arch/x86/include/asm/syscalls.h
> arch/x86/kernel/signal.c
>
> diff --git a/arch/x86/kernel/signal.c b/arch/x86/kernel/signal.c
> index b1f4d34..b1cc6da 100644 (file)
> --- a/arch/x86/kernel/signal.c
> +++ b/arch/x86/kernel/signal.c
> @@ -642,11 +642,9 @@ badframe:
> }
>
> #ifdef CONFIG_X86_32
> -asmlinkage int sys_rt_sigreturn(unsigned long __unused)
> +asmlinkage int sys_rt_sigreturn(struct pt_regs regs)
> {
> - struct pt_regs *regs = (struct pt_regs *)&__unused;
This probably should have been converted to
asmlinkage long sys_rt_sigreturn(void)
{
struct pt_regs *regs = task_pt_regs(current);
[...]
> -
> - return do_rt_sigreturn(regs);
> + return do_rt_sigreturn(®s);
> }
> #else /* !CONFIG_X86_32 */
> asmlinkage long sys_rt_sigreturn(struct pt_regs *regs)
Also there's no reason to have different sys_rt_sigreturn implementations
for 32 and 64 bit. They just could be merged with do_rt_sigreturn.
prev parent reply other threads:[~2009-01-20 7:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 20:56 Justin Madru
2009-01-17 2:28 ` Justin Madru
2009-01-17 3:27 ` John Stoffel
2009-01-17 3:27 ` Justin P. Mattock
2009-01-17 8:48 ` Justin Madru
2009-01-17 9:10 ` Justin P. Mattock
2009-01-17 20:21 ` Jesper Juhl
2009-01-17 21:07 ` Justin Madru
2009-01-17 22:51 ` Justin P. Mattock
2009-01-18 0:05 ` Justin Madru
2009-01-18 0:46 ` Justin P. Mattock
2009-01-18 2:06 ` Justin Madru
2009-01-18 2:49 ` Justin P. Mattock
2009-01-20 0:32 ` [bisected] " Justin Madru
2009-01-20 1:06 ` Justin P. Mattock
2009-01-20 1:25 ` Hiroshi Shimamoto
2009-01-20 6:19 ` Justin Madru
2009-01-20 18:28 ` Hiroshi Shimamoto
2009-01-20 19:22 ` Justin Madru
2009-01-20 19:48 ` Hiroshi Shimamoto
2009-01-21 2:39 ` Justin Madru
2009-01-21 3:04 ` Hiroshi Shimamoto
2009-01-20 1:39 ` Peter Annema
2009-01-20 7:15 ` Heiko Carstens [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=20090120071555.GA6165@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=jdm64@gawab.com \
--cc=jj@chaosbits.net \
--cc=john@stoffel.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome