[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <537BADAD.5070904@gmail.com>
Date: Tue, 20 May 2014 21:31:57 +0200
From: Tomasz Figa <tomasz.figa@...il.com>
To: Andrew Eikum <aeikum@...eweavers.com>
CC: Rickard Strandqvist <rickard_strandqvist@...ctrumdigital.se>,
Mark Brown <broonie@...nel.org>, alsa-devel@...a-project.org,
Kukjin Kim <kgene.kim@...sung.com>,
Sangbeom Kim <sbkim73@...sung.com>,
linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
Takashi Iwai <tiwai@...e.de>,
linux-samsung-soc@...r.kernel.org, Ben Dooks <ben-linux@...ff.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [alsa-devel] [PATCH] Fix for possible null pointer dereference
in dma.c
On 20.05.2014 21:29, Andrew Eikum wrote:
> On Tue, May 20, 2014 at 09:16:59PM +0200, Tomasz Figa wrote:
>> To me having NULL as either data argument of buffer done callback or
>> private_data would be a serious driver bug and IMHO it's better to let
>> it crash with a NULL pointer dereference to let someone notice than mask
>> it by adding a condition.
>>
>
> Please, no. Regardless of who is at fault, crashes in library code
> are insanely frustrating to application developers. Error codes can
> be handled nicely and expressed to the user as an error message.
> Crashes are hideous for end users and usually end up being support
> nightmares for developers.
How is the related code a library?
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists