linux-kernel - Re: post 3.5, phantom signals.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 01 Aug 2012 20:57:56 -0400
From:	fche@...hat.com (Frank Ch. Eigler)
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: post 3.5, phantom signals.

Oleg Nesterov <oleg@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/