All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: post 3.5, phantom signals.
Date: Wed, 1 Aug 2012 11:50:28 -0400	[thread overview]
Message-ID: <20120801155028.GA26424@redhat.com> (raw)
In-Reply-To: <20120801151134.GA9333@redhat.com>

On Wed, Aug 01, 2012 at 05:11:34PM +0200, Oleg Nesterov wrote:
 > On 07/31, Dave Jones wrote:
 > >
 > > Since 3.5, I've started noticing weird things happening with signal delivery.
 > > Things I've seen so far..
 > >
 > > - long running tasks SIGINT, even though I wasn't even anywhere near the keyboard.
 > > - processes running inside screen/tmux disappearing (and taking the whole session with them).
 > >
 > > And now, while waiting for a kernel to build I just saw..
 > >
 > > /bin/sh: line 1:  3274 Hangup                  gcc
 > 
 > Currently I have no idea where this change could come from...
 > 
 > Well, not sure this will help... but if you can reproduce this,
 > may be you can identify the sender of the wrong SIGHUP at least.
 > 
 > 	cd /sys/kernel/debug/tracing/
 > 	echo "sig==1" >> events/signal/signal_generate/filter
 > 	echo 1 >> options/stacktrace
 > 	echo 1 >> events/signal/signal_generate/enable
 > 	cat trace_pipe > SIGHUP_TRACE
 > 
 > and then rebuild the kernel.

I'll give that a shot when I'm back on running kernel of the day.
Right now, I'm bisecting something that requires an hour or so of testing
between each step, so that's pretty much written off this week.

	Dave


  reply	other threads:[~2012-08-01 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 19:17 post 3.5, phantom signals Dave Jones
2012-07-31 20:10 ` Linus Torvalds
2012-08-01 15:11 ` Oleg Nesterov
2012-08-01 15:50   ` Dave Jones [this message]
2012-08-02  0:57   ` Frank Ch. Eigler

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=20120801155028.GA26424@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=torvalds@linux-foundation.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.