[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130225150534.269bacc4.akpm@linux-foundation.org>
Date: Mon, 25 Feb 2013 15:05:34 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Mandeep Singh Baines <msb@...omium.org>,
Neil Horman <nhorman@...hat.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Tejun Heo <tj@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm 0/3] coredump: make it freezable (almost)
On Sun, 24 Feb 2013 18:31:44 +0100
Oleg Nesterov <oleg@...hat.com> wrote:
> Hello.
>
> On top of coredump-sanitize-the-setting-of-signal-group_exit_code.patch
>
> Andrew, "almost" means we need a bit more changes, but these
> changes should be absolutely trivial/straightforward. We need
> to add the killable/freezeng checks in dump_write/seek. But this
> depends on 2/3, lets discuss this series first.
Thanks. I still have these marked "for 3.10".
coredump-only-sigkill-should-interrupt-the-coredumping-task.patch
coredump-ensure-that-sigkill-always-kills-the-dumping-thread.patch
coredump-sanitize-the-setting-of-signal-group_exit_code.patch
coredump-factor-out-the-setting-of-pf_dumpcore.patch
freezer-do-not-send-a-fake-signal-to-a-pf_dumpcore-thread.patch
coredump-make-wait_for_dump_helpers-freezable.patch
--
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/
Powered by blists - more mailing lists