From: Oleg Nesterov <oleg@tv-sign.ru>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coredump: elf_core_dump: skip kernel threads
Date: Sat, 28 Jun 2008 17:36:28 +0400 [thread overview]
Message-ID: <20080628133628.GA4434@tv-sign.ru> (raw)
In-Reply-To: <20080627204953.C2A49154224@magilla.localdomain>
On 06/19, Roland McGrath wrote:
>
> Perhaps a little prettier like this:
>
> --- a/fs/binfmt_elf.c
> +++ b/fs/binfmt_elf.c
> @@ -1469,6 +1469,12 @@ static int fill_thread_core_info(struct
> return 1;
> }
>
> +static bool is_dump_thread(struct task_struct *dump_task,
> + struct task_struct *thread)
> +{
> + return !(thread->flags & PF_KTHREAD) && thread->mm == dump_task->mm;
> +}
> +
> static int fill_note_info(struct elfhdr *elf, int phdrs,
> struct elf_note_info *info,
> long signr, struct pt_regs *regs)
> @@ -1518,7 +1524,7 @@ static int fill_note_info(struct elfhdr
> */
> rcu_read_lock();
> do_each_thread(g, p)
> - if (p->mm == dump_task->mm) {
> + if (is_dump_thread(dump_task, p)) {
> t = kzalloc(offsetof(struct elf_thread_core_info,
> notes[info->thread_notes]),
> GFP_ATOMIC);
Agreed.
> > It is sad we have to iterate over all threads in system and use GFP_ATOMIC.
> > Hopefully we can kill theses ugly do_each_thread()s, but this needs some
> > nontrivial changes in mm_struct and do_coredump.
>
> Agreed, and twice at that (coredump_wait). But this is something more to
> consider for the future, and I wouldn't worry about it right now.
In most cases coredump_wait() doesn't need to do for_each_process().
And I think there are other reasons to kill these do_each_thread()s.
We can simplify the code and make the coredumping process visible to
oom_kill. I sent the preparatory patches.
Oleg.
prev parent reply other threads:[~2008-06-28 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 16:26 Oleg Nesterov
2008-06-19 7:19 ` Roland McGrath
2008-06-28 13:36 ` Oleg Nesterov [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=20080628133628.GA4434@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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
all inboxes | Powered by JetHome®