From: fche@redhat.com (Frank Ch. Eigler)
To: Oleg Nesterov <oleg@redhat.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: post 3.5, phantom signals.
Date: Wed, 01 Aug 2012 20:57:56 -0400 [thread overview]
Message-ID: <y0m7gtiun3f.fsf@fche.csb> (raw)
In-Reply-To: <20120801151134.GA9333@redhat.com> (Oleg Nesterov's message of "Wed, 1 Aug 2012 17:11:34 +0200")
Oleg Nesterov <oleg@redhat.com> writes:
> [...]
> 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
FWIW, just in case your ftrace subsystem is already busy, this
two-liner is equivalent:
# stap -o SIGHUP_TRACE -e 'probe kernel.trace("signal_generate")
{ if ($sig==1) print_backtrace() }'
- FChE
prev parent reply other threads:[~2012-08-02 0:58 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
2012-08-02 0:57 ` Frank Ch. Eigler [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=y0m7gtiun3f.fsf@fche.csb \
--to=fche@redhat.com \
--cc=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.