mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>,
	Andrew Collins <bsderandrew@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.0.70
Date: Wed, 20 Mar 2013 17:15:50 -0700	[thread overview]
Message-ID: <20130321001550.GB27981@kroah.com> (raw)
In-Reply-To: <CAKTPYJQeCW2fGy3bb6G2uxeQN2WYgeA63_7Lwt9ytpcwZwrnQA@mail.gmail.com>

On Wed, Mar 20, 2013 at 04:04:19PM -0600, Andrew Collins wrote:
> Kees Cook (1):
>       signal: always clear sa_restorer on execve
> 
> This commit seems to cause the following build breakage on MIPS in 3.0.70:
> 
> kernel/signal.c: In function 'flush_signal_handlers':
> kernel/signal.c:441:9: error: 'struct sigaction' has no member named
> 'sa_restorer'
> make[3]: *** [kernel/signal.o] Error 1
> make[2]: *** [kernel] Error 2
> make[2]: *** Waiting for unfinished jobs....
> 
> I'm testing with a variety of additional patches applied and it's a
> bit difficult to test vanilla, but this looks unrelated to my local
> patches.  Looks like MIPS defines SA_RESTORER but doesn't have a
> sa_restorer in sigaction so:
> 
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -437,6 +437,9 @@ flush_signal_handlers(struct task_struct *t, int
> force_default)
>                 if (force_default || ka->sa.sa_handler != SIG_IGN)
>                         ka->sa.sa_handler = SIG_DFL;
>                 ka->sa.sa_flags = 0;
> +#ifdef SA_RESTORER
> +               ka->sa.sa_restorer = NULL;
> +#endif
>                 sigemptyset(&ka->sa.sa_mask);
>                 ka++;
>         }
> 
> goes kaboom.

Kees, I'm getting a number of bug reports that this patch breaks MIPS on
all of the recent stable kernel releases (3.0, 3.4, 3.8).

Any hints on a fix?

thanks,

greg k-h

  parent reply	other threads:[~2013-03-21  0:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 22:04 Andrew Collins
2013-03-20 22:38 ` Shuah Khan
2013-03-21  0:15 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-20 20:14 Greg KH
2013-03-20 20:14 ` Greg KH

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=20130321001550.GB27981@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bsderandrew@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®