From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751850AbdK2SUE (ORCPT ); Wed, 29 Nov 2017 13:20:04 -0500 Received: from mout.web.de ([212.227.17.12]:65085 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750713AbdK2SUB (ORCPT ); Wed, 29 Nov 2017 13:20:01 -0500 Subject: Re: jsm_tty: Fix a possible null pointer dereference in two functions To: Greg Kroah-Hartman , linux-serial@vger.kernel.org Cc: Joe Perches , "Guilherme G. Piccoli" , Jiri Slaby , LKML , kernel-janitors@vger.kernel.org References: <5c78db97-88f5-8655-9a47-eeee0a043fba@users.sourceforge.net> <1511976187.19952.65.camel@perches.com> <20171129173504.GA20581@kroah.com> <1511977896.19952.69.camel@perches.com> <20171129180528.GA24705@kroah.com> From: SF Markus Elfring Message-ID: <089a4b85-64e8-cb4a-c5f8-9abb2556e5e5@users.sourceforge.net> Date: Wed, 29 Nov 2017 19:19:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171129180528.GA24705@kroah.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:bI8Y4kTvlXsDfx0JS+sUmFHU2JJiZ3lWCSx9ECgnVjdiugxDwOX zGjeuaqNUpqIVyMc1Zm3DgxOEYY4XDrm2F0L0AKs0fCEXCVEssH3fO3oyvs9K4jHqz1zD/R eCsYzcuV801QhxVjQ6HSkHbXEfRmVYhRkO9dTINXERHxAPuki9GZMJ+lrTT47hPEUzhDQaC D0peFGcOKwBue1W1B+zrA== X-UI-Out-Filterresults: notjunk:1;V01:K0:wTLdknTqn/4=:D1FGHaO6uMW80HxMbPV8j7 lFjZ1JLRQyFUTwUFHefol7A0giCFvJZpBpMKEPQq5Ev7PsDRK0lQFhxW9xzr5SZvsVF+TFeHx 3C3MYX9cmobBURybeH49GC2aVk43jk1wZ1ILGeYrGPSUpO63USSDtD/gqlfwDwkeGi533AIu2 UsyI0q8pWGa6wC6lrvkiRYeR45Fl9wPrAuZBJLnT4SEY3fsEdrScUGAuvcgmLwEU0bHlOADLA cIQ2108FnXv0FN1ec8SDnlZ+PKqs2cSXCiUMyryfBhIBTJblPu4tUHVilsuf/vUTDob2PAVvS op1msI4H+Dk+0i5oP1bhTuWT9UkG+qwy1RhfJ7qXBr9SdvoA6sth1UVpfW4kdqpuWz/oAaDke tunz4jJjXYn+rvFF7Gaoz5BlEiTQVx7uT5AOc6j6OZA1S09QDlk9pJtOrutQPA+bJd9gBPMSL NNiA4s6ECfYSrNxInRL6cK5JxSSqACM66y+xb824fC0ymFTgwwB41trFI1diPVZIFiCrxlajA 6lYG7JEdxPRCkTu7/zqNo7X4AsjncVbGJ0QiorhnSRGKrU+BeO7YwVLoV8lvq2VedLx+nQ9QJ M65xJt7BR5XxEpSxu3vTYUmbJYry2LlcXRWnJyRtw8G72cTZnNWAuZBxOaR8ltMPXo4QN+rBZ SWdpQMWMyPpMNm6sGQ3pfQ7fvbTffpKpXZS5t1P53DfwbK8XbMRymkywdXNIEFS/NhNtCJQyp d1Xc65A7KaXDB8z8VE/iWcADxt1YY+ZNVYsEQ/xLC0acJ31aSHCqBV0wFk7VeWEwtafi60c50 8UvBLspVoridCZzIGDTonjm1CK84RS4Y6roGxrL/az6id26v6n9b4BtexOtmT116VBsuMwn Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> It's pretty unlikely, but it is an actual defect. > > No it is not, those variables will never be set to NULL, > so this can never be triggered. Walk up the call chain. If the involved software developers are convinced about the validity of this pointer: How do you think about to delete the following condition check instead in the discussed function implementations? if (!ch) return; Regards, Markus