kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linux do_coredump() and SMP systems
Date: Tue, 17 Feb 2015 07:12:06 -0800	[thread overview]
Message-ID: <20150217151206.GB18008@kroah.com> (raw)
In-Reply-To: <CAP0SO-Esv+U2sgCwCqm+fJ7r7unhgEcE4-XGY-+9gfiAm9XpuA@mail.gmail.com>

On Tue, Feb 17, 2015 at 07:11:55PM +0530, Sudharsan Vijayaraghavan wrote:
> Hi All,
> 
> We are running 3.8 kernel.

That's pretty old and obsolete, why are you stuck with that version?

> I have a unique scenario, where we hit on several issues in do_coredump.
> We have a SMP system with thousands of cores, one pthread is tied to
> one core. The main process containing these pthreads runs in the first
> core.
> 
> Here is the issue # 1
> When one of threads core dump, we enter into do_coredump(), now one
> other thread in same process running in a different
> core can as well core dump(before SIGKILL was delivered to it as a
> consequence of first core dump)
> This gives way to entering into do_coredump more than once.
> Once we have two guys entering do_coredump() one can kill other with SIGKILL
> the result is completely unpredictable. No guarantee we will have two
> core files generated in the end
> 
> Linux kernel does not seem to handle it at all.
> Adding a spin lock within do_coredump() will solve the case of
> multiple entries into do_coredump()
> 
> I want to know whether Linux kernel really does not handle the above
> case or am I missing something?

Odd, we should handle this just fine, try emailing the developers
responsible for this code and cc: the linux-kernel mailing list so they
can work it out.

thanks,

greg k-h

  reply	other threads:[~2015-02-17 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 13:41 Linux do_coredump() and SMP systems Sudharsan Vijayaraghavan
2015-02-17 15:12 ` Greg KH [this message]
     [not found]   ` <CAP0SO-GBmpMS168SRNAdFmStknC=+4EuAENCvuiaX=mXRvr7hg@mail.gmail.com>
2015-02-18  6:14     ` Sudharsan Vijayaraghavan
2015-02-18 16:01       ` Greg KH
2015-02-19 12:00         ` Sudharsan Vijayaraghavan

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=20150217151206.GB18008@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).