From: Mandeep Singh Baines <mandeep.baines@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Ben Chan <benchan@chromium.org>,
Mandeep Singh Baines <msb@chromium.org>,
Oleg Nesterov <oleg@redhat.com>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@redhat.com>
Subject: [PATCH v3] coredump: ignore non-fatal signals when core dumping to a pipe
Date: Fri, 15 Feb 2013 16:09:58 -0800 [thread overview]
Message-ID: <1360973398-23823-1-git-send-email-msb@chromium.org> (raw)
In-Reply-To: <1360885096-21207-5-git-send-email-msb@chromium.org>
From: Ben Chan <benchan@chromium.org>
Make wait_for_dump_helpers() not abort piping the core dump data when the
crashing process has received a non-fatal signal. The abort still occurs
in the case of SIGKILL.
Addresses http://crosbug.com/21559
Changes since v1:
* Mandeep Singh Baines
* To prevent blocking suspend, add try_to_freeze().
Changes since v2:
* LKML: <20130215150117.GB30829@redhat.com> Oleg Nestorov
* Block non-fatal signals to avoid poll_wait busy waiting.
* LKML: <20130215152538.9a61a44e.akpm@linux-foundation.org> Andrew Morton
* Added comment re: try_to_freeze and clarified commit message.
Signed-off-by: Ben Chan <benchan@chromium.org>
Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
CC: Oleg Nesterov <oleg@redhat.com>
CC: Tejun Heo <tj@kernel.org>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Rafael J. Wysocki <rjw@sisk.pl>
CC: Ingo Molnar <mingo@redhat.com>
---
fs/coredump.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/fs/coredump.c b/fs/coredump.c
index 1774932..976f6cc 100644
--- a/fs/coredump.c
+++ b/fs/coredump.c
@@ -32,6 +32,7 @@
#include <linux/pipe_fs_i.h>
#include <linux/oom.h>
#include <linux/compat.h>
+#include <linux/freezer.h>
#include <asm/uaccess.h>
#include <asm/mmu_context.h>
@@ -410,6 +411,11 @@ static void coredump_finish(struct mm_struct *mm)
static void wait_for_dump_helpers(struct file *file)
{
struct pipe_inode_info *pipe;
+ sigset_t blocked, previous;
+
+ /* Block all but fatal signals. */
+ siginitsetinv(&blocked, sigmask(SIGKILL));
+ sigprocmask(SIG_BLOCK, &blocked, &previous);
pipe = file->f_path.dentry->d_inode->i_pipe;
@@ -421,12 +427,22 @@ static void wait_for_dump_helpers(struct file *file)
wake_up_interruptible_sync(&pipe->wait);
kill_fasync(&pipe->fasync_readers, SIGIO, POLL_IN);
pipe_wait(pipe);
+
+ /*
+ * Non-fatal signals are blocked. So we need to try
+ * to freeze in order to not block suspend.
+ */
+ pipe_unlock(pipe);
+ try_to_freeze();
+ pipe_lock(pipe);
}
pipe->readers--;
pipe->writers++;
pipe_unlock(pipe);
+ /* Restore signals. */
+ sigprocmask(SIG_SETMASK, &previous, NULL);
}
/*
--
1.7.12.4
next prev parent reply other threads:[~2013-02-16 0:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 23:38 [PATCH 1/5] vfork: don't freezer_count() for in-kernel users of CLONE_VFORK Mandeep Singh Baines
2013-02-14 23:38 ` [PATCH 2/5] lockdep: check that no locks held at freeze time Mandeep Singh Baines
2013-02-15 11:16 ` Ingo Molnar
2013-02-15 15:44 ` Oleg Nesterov
2013-02-14 23:38 ` [PATCH 3/5] coredump: cleanup the waiting for coredump_finish code Mandeep Singh Baines
2013-02-15 14:53 ` Oleg Nesterov
2013-02-15 23:30 ` Andrew Morton
2013-02-14 23:38 ` [PATCH 4/5] coredump: use a freezable_schedule for the coredump_finish wait Mandeep Singh Baines
2013-02-14 23:38 ` [PATCH 5/5] coredump: abort core dump piping only due to a fatal signal Mandeep Singh Baines
2013-02-15 15:01 ` Oleg Nesterov
2013-02-16 1:20 ` Mandeep Singh Baines
2013-02-16 17:05 ` Oleg Nesterov
2013-02-15 23:25 ` Andrew Morton
2013-02-16 0:09 ` Mandeep Singh Baines [this message]
2013-02-16 0:57 ` [PATCH v4] coredump: ignore non-fatal signals when core dumping to a pipe Mandeep Singh Baines
2013-02-15 15:28 ` [PATCH 1/5] vfork: don't freezer_count() for in-kernel users of CLONE_VFORK Oleg Nesterov
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=1360973398-23823-1-git-send-email-msb@chromium.org \
--to=mandeep.baines@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benchan@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=msb@chromium.org \
--cc=oleg@redhat.com \
--cc=rjw@sisk.pl \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).