From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Maninder Singh <maninder1.s@samsung.com>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
mark.rutland@arm.com, jack@suse.cz, linux-kernel@vger.kernel.org,
ajeet.y@samsung.com, shijie.huang@arm.com, james.morse@arm.com,
sandeepa.s.prabhu@gmail.com, labbott@redhat.com,
Amit Nagal <amit.nagal@samsung.com>,
linux-arm-kernel@lists.infradead.org, pankaj.m@samsung.com
Subject: Re: [PATCH 1/1] mm: call force_sig_info before prints
Date: Mon, 19 Dec 2016 11:07:35 +0000 [thread overview]
Message-ID: <20161219110735.GR14217@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1482143832-11158-1-git-send-email-maninder1.s@samsung.com>
On Mon, Dec 19, 2016 at 04:07:12PM +0530, Maninder Singh wrote:
> prints can delay queuing of signal, so better to print
> after force_sig_info.
>
> Let's say process generated SIGSEGV , and some other thread sends
> SIGKILL to crashing process and it gets queued before SIGSEGV becuase
> of little delay due to prints so in this case coredump might not generate.
In any case, that's going to be a race - you can't predict exactly when
the "other thread" will send the SIGKILL in relation to the SIGSEGV.
So, I don't see the point of this change.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-12-19 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 10:37 [PATCH 1/1] mm: call force_sig_info before prints Maninder Singh
2016-12-19 11:07 ` Russell King - ARM Linux [this message]
[not found] ` <CGME20161219110753epcas3p1e2a8b5ce7bd4b4e26345f28ae803d72b@epcas3p1.samsung.com>
[not found] ` <20161221055911epcms5p1146cee9212cc17fa8d5b18c49a085def@epcms5p1>
2016-12-21 9:21 ` Russell King - ARM Linux
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=20161219110735.GR14217@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ajeet.y@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=amit.nagal@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=jack@suse.cz \
--cc=james.morse@arm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=mark.rutland@arm.com \
--cc=pankaj.m@samsung.com \
--cc=sandeepa.s.prabhu@gmail.com \
--cc=shijie.huang@arm.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).