From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751409AbbEYRPJ (ORCPT ); Mon, 25 May 2015 13:15:09 -0400 Received: from a.ns.miles-group.at ([95.130.255.143]:65275 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750800AbbEYRPG (ORCPT ); Mon, 25 May 2015 13:15:06 -0400 Message-ID: <55635896.1040600@nod.at> Date: Mon, 25 May 2015 19:15:02 +0200 From: Richard Weinberger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Oleg Nesterov CC: airlied@linux.ie, dri-devel@lists.freedesktop.org, "linux-kernel@vger.kernel.org" Subject: Re: block_all_signals() usage in DRM References: <556338DA.6000404@nod.at> <20150525165032.GB32370@redhat.com> In-Reply-To: <20150525165032.GB32370@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 25.05.2015 um 18:50 schrieb Oleg Nesterov: > AAAAOn 05/25, Richard Weinberger wrote: >> >> Is this functionality still in use/needed? > > All I can say it doesn't work. > >> Otherwise we could get rid of block_all_signals() and unpuzzle the signaling >> code a bit. :-) > > Yes. I do not even remember when I reported this the first time. Perhaps > more than 10 years ago. > > See the last attempt in 2011: https://lkml.org/lkml/2011/7/12/263 > I copied this email below. Thank you Oleg, this makes sense. I was actually wondering WTF this function is good for. Thanks, //richard