All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>,
	linux-kernel@vger.kernel.org,
	Matt Fleming <matt.fleming@linux.intel.com>
Subject: Re: [PATCH] avr32: init cannot ignore signals sent by force_sig_info()
Date: Mon, 4 Apr 2011 18:04:47 +0200	[thread overview]
Message-ID: <20110404160447.GB23655@redhat.com> (raw)
In-Reply-To: <1301929084-2025-1-git-send-email-matt@console-pimps.org>

On 04/04, Matt Fleming wrote:
>
> --- a/arch/avr32/kernel/traps.c
> +++ b/arch/avr32/kernel/traps.c
> @@ -95,28 +95,6 @@ void _exception(long signr, struct pt_regs *regs, int code,
>  	info.si_code = code;
>  	info.si_addr = (void __user *)addr;
>  	force_sig_info(signr, &info, current);
> -
> -	/*
> -	 * Init gets no signals that it doesn't have a handler for.
> -	 * That's all very well, but if it has caused a synchronous
> -	 * exception and we ignore the resulting signal, it will just
> -	 * generate the same exception over and over again and we get
> -	 * nowhere.  Better to kill it and let the kernel panic.
> -	 */
> -	if (is_global_init(current)) {
> -		__sighandler_t handler;
> -
> -		spin_lock_irq(&current->sighand->siglock);
> -		handler = current->sighand->action[signr-1].sa.sa_handler;
> -		spin_unlock_irq(&current->sighand->siglock);
> -		if (handler == SIG_DFL) {
> -			/* init has generated a synchronous exception
> -			   and it doesn't have a handler for the signal */
> -			printk(KERN_CRIT "init has generated signal %ld "
> -			       "but has no handler for it\n", signr);
> -			do_exit(signr);
> -		}
> -	}

Reviewed-by: Oleg Nesterov <oleg@redhat.com>


  reply	other threads:[~2011-04-04 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 14:58 [PATCH] avr32: init cannot ignore signals sent by force_sig_info() Matt Fleming
2011-04-04 16:04 ` Oleg Nesterov [this message]
2011-04-13 13:14 ` Hans-Christian Egtvedt

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=20110404160447.GB23655@redhat.com \
    --to=oleg@redhat.com \
    --cc=hans-christian.egtvedt@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@linux.intel.com \
    --cc=matt@console-pimps.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.