From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: [patch] log fatal signals like SIGSEGV
Date: Fri, 12 Sep 2008 19:11:09 +0200 [thread overview]
Message-ID: <20080912171055.GA5532@joi> (raw)
In-Reply-To: <200809121502.15264.thomas.jarosch@intra2net.com>
On Fri, Sep 12, 2008 at 03:02:14PM +0200, Thomas Jarosch wrote:
> --------------------------------------------------------
> Log fatal signals like SIGSEGV or SIGBUS
Note that on current kernel when process segfaults it printks:
a.out[5974]: segfault at 0 ip 00000000004004c1 sp 00007fffdd1a3ce0 error 6 in a.out[400000+1000]
> to aid debugging of obscure problems.
>
> The code is a stripped down version
> of grsecurity's signal logger.
>
> Signed-Off-By: Gerd v. Egidy <gve@intra2net.com>
> Signed-Off-By: Thomas Jarosch <thomas.jarosch@intra2net.com>
Please look at Documentation/SubmittingPatches.
(Signed-off-by capitalization and lack of (?) From field)
>
> diff -u -r -p linux-2.6.22/kernel/signal.c linux.siglog/kernel/signal.c
> --- linux-2.6.22/kernel/signal.c Mon Jul 9 01:32:17 2007
> +++ linux.siglog/kernel/signal.c Wed Aug 22 11:08:58 2007
> @@ -514,6 +514,64 @@ static int rm_from_queue(unsigned long m
> }
>
> /*
> + * Stuff needed for signal logger
> + */
> +
> +spinlock_t siglog_lock = SPIN_LOCK_UNLOCKED;
Please use DEFINE_SPINLOCK if spinlock is really needed (look below).
> +unsigned long volatile siglog_wtime = 0;
> +unsigned long volatile siglog_fyet = 0;
> +
> +/* time span in which flooding is measured */
> +#define SIGLOG_FLOOD_SECONDS 5
> +
> +/* how many log entries are allowed in this time span */
> +#define SIGLOG_FLOOD_BURST_LINES 20
> +
> +/*
> + * Log fatal signals
> + */
> +void
> +log_fatal_signal(const int sig, const struct task_struct *t)
> +{
> + if ((sig == SIGSEGV) || (sig == SIGILL) || (sig == SIGABRT)
> + || (sig == SIGBUS) || (sig == SIGKILL) || (sig == SIGFPE)) {
It would be clearer if you could write this code as:
if (!sth)
return;
do_other_stuff;
> +
> + /* flood protection */
> + spin_lock(&siglog_lock);
> + if (!siglog_wtime || jiffies - siglog_wtime > SIGLOG_FLOOD_SECONDS * HZ) {
> + /* no logging activity yet */
> + siglog_wtime = jiffies;
> + siglog_fyet = 0;
> + } else if ((jiffies - siglog_wtime <= SIGLOG_FLOOD_SECONDS * HZ)
> + && (siglog_fyet < SIGLOG_FLOOD_BURST_LINES)) {
> + /* logging within SIGLOG_FLOOD_SECONDS, but below threshold */
> + siglog_fyet++;
> + } else {
> + /* flooding detected, warn once and return */
> + if (siglog_fyet == SIGLOG_FLOOD_BURST_LINES) {
> + siglog_wtime = jiffies;
> + siglog_fyet++;
> + printk(KERN_ALERT "siglog: more alerts, logging disabled for"
> + " %d seconds\n", SIGLOG_FLOOD_SECONDS);
> + }
> + spin_unlock(&siglog_lock);
> + return;
> + }
> + spin_unlock(&siglog_lock);
You probably want to use printk_ratelimit or DEFINE_RATELIMIT_STATE/__ratelimit.
> +
> + read_lock(&tasklist_lock);
> + printk(KERN_WARNING "signal %d sent to %.30s[%d] uid:%u, "
> + "parent %.30s[%d] uid:%u by %.30s[%d] uid:%u, "
> + "parent %.30s[%d] uid:%u\n", sig, t->comm, t->pid, t->uid,
> + t->parent->comm, t->parent->pid, t->parent->uid,
> + current->comm, current->pid, current->uid,
> + current->parent->comm, current->parent->pid, current->parent->uid);
> + read_unlock(&tasklist_lock);
> + }
> + return;
> +}
> +
> +/*
> * Bad permissions for sending the signal
> */
> static int check_kill_permission(int sig, struct siginfo *info,
> @@ -536,6 +594,8 @@ static int check_kill_permission(int sig
> && !capable(CAP_KILL))
> return error;
>
> + log_fatal_signal(sig, t);
> +
> return security_task_kill(t, info, sig, 0);
> }
>
> @@ -773,6 +833,9 @@ force_sig_info(int sig, struct siginfo *
> }
> }
> ret = specific_send_sig_info(sig, info, t);
> +
> + log_fatal_signal(sig, t);
> +
> spin_unlock_irqrestore(&t->sighand->siglock, flags);
>
> return ret;
>
> --
Marcin
next prev parent reply other threads:[~2008-09-12 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 13:02 RFC: [patch] log fatal signals like SIGSEGV Thomas Jarosch
2008-09-12 17:11 ` Marcin Slusarz [this message]
2008-09-16 12:59 ` Thomas Jarosch
2008-09-16 17:42 ` Marcin Slusarz
2008-09-17 8:12 ` Thomas Jarosch
2008-09-18 10:10 ` Thomas Jarosch
2008-09-18 20:20 ` Marcin Slusarz
2008-09-20 17:12 ` Thomas Jarosch
2008-09-21 19:05 ` Mikael Pettersson
2008-09-21 19:15 ` Bernd Eckenfels
2008-09-21 19:40 ` Mikael Pettersson
2008-10-06 8:53 ` Thomas Jarosch
2008-09-22 23:52 ` Jiri Kosina
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=20080912171055.GA5532@joi \
--to=marcin.slusarz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.jarosch@intra2net.com \
/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