linux-kernel - Re: [PATCH 1/1] mm: call force_sig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20161219110735.GR14217@n2100.armlinux.org.uk>
Date:   Mon, 19 Dec 2016 11:07:35 +0000
From:   Russell King - ARM Linux <linux@...linux.org.uk>
To:     Maninder Singh <maninder1.s@...sung.com>
Cc:     catalin.marinas@....com, will.deacon@....com,
        akpm@...ux-foundation.org, kirill.shutemov@...ux.intel.com,
        mark.rutland@....com, jack@...e.cz, linux-kernel@...r.kernel.org,
        ajeet.y@...sung.com, shijie.huang@....com, james.morse@....com,
        sandeepa.s.prabhu@...il.com, labbott@...hat.com,
        Amit Nagal <amit.nagal@...sung.com>,
        linux-arm-kernel@...ts.infradead.org, pankaj.m@...sung.com
Subject: Re: [PATCH 1/1] mm: call force_sig_info before prints

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.