All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: coverity-bot <keescook@chromium.org>, Lyude Paul <lyude@redhat.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	linux-kernel@vger.kernel.org, Ilia Mirkin <imirkin@alum.mit.edu>,
	Daniel Vetter <daniel@ffwll.ch>,
	Karol Herbst <kherbst@redhat.com>,
	Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@gmail.com>,
	"Nathan E. Egge" <unlord@xiph.org>,
	dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
	Dave Airlie <airlied@redhat.com>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: Coverity: nouveau_dp_irq(): Null pointer dereferences
Date: Fri, 11 Nov 2022 11:13:17 +0200	[thread overview]
Message-ID: <87iljl6ehe.fsf@intel.com> (raw)
In-Reply-To: <202211100850.7A8DD75@keescook>

On Thu, 10 Nov 2022, coverity-bot <keescook@chromium.org> wrote:
> Hello!
>
> This is an experimental semi-automated report about issues detected by
> Coverity from a scan of next-20221110 as part of the linux-next scan project:
> https://scan.coverity.com/projects/linux-next-weekly-scan
>
> You're getting this email because you were associated with the identified
> lines of code (noted below) that were touched by commits:
>
>   Mon Aug 31 19:10:08 2020 -0400
>     a0922278f83e ("drm/nouveau/kms/nv50-: Refactor and cleanup DP HPD handling")

Hi Kees, this looks like a good idea, but maybe double check the Cc list
generation? I was Cc'd on four mails today that I thought were
irrelevant to me.

Thanks,
Jani.

>
> Coverity reported the following:
>
> *** CID 1527266:  Null pointer dereferences  (REVERSE_INULL)
> drivers/gpu/drm/nouveau/nouveau_dp.c:237 in nouveau_dp_irq()
> 231     	struct nouveau_encoder *outp = find_encoder(connector, DCB_OUTPUT_DP);
> 232     	struct nouveau_drm *drm = nouveau_drm(outp->base.base.dev);
> 233     	struct nv50_mstm *mstm;
> 234     	u64 hpd = 0;
> 235     	int ret;
> 236
> vvv     CID 1527266:  Null pointer dereferences  (REVERSE_INULL)
> vvv     Null-checking "outp" suggests that it may be null, but it has already been dereferenced on all paths leading to the check.
> 237     	if (!outp)
> 238     		return;
> 239
> 240     	mstm = outp->dp.mstm;
> 241     	NV_DEBUG(drm, "service %s\n", connector->name);
> 242
>
> If this is a false positive, please let us know so we can mark it as
> such, or teach the Coverity rules to be smarter. If not, please make
> sure fixes get into linux-next. :) For patches fixing this, please
> include these lines (but double-check the "Fixes" first):
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1527266 ("Null pointer dereferences")
> Fixes: a0922278f83e ("drm/nouveau/kms/nv50-: Refactor and cleanup DP HPD handling")
>
> Thanks for your attention!

-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: coverity-bot <keescook@chromium.org>, Lyude Paul <lyude@redhat.com>
Cc: "Nathan E. Egge" <unlord@xiph.org>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-next@vger.kernel.org,
	Ben Skeggs <bskeggs@redhat.com>, Daniel Vetter <daniel@ffwll.ch>,
	Dave Airlie <airlied@redhat.com>,
	linux-hardening@vger.kernel.org
Subject: Re: [Nouveau] Coverity: nouveau_dp_irq(): Null pointer dereferences
Date: Fri, 11 Nov 2022 11:13:17 +0200	[thread overview]
Message-ID: <87iljl6ehe.fsf@intel.com> (raw)
In-Reply-To: <202211100850.7A8DD75@keescook>

On Thu, 10 Nov 2022, coverity-bot <keescook@chromium.org> wrote:
> Hello!
>
> This is an experimental semi-automated report about issues detected by
> Coverity from a scan of next-20221110 as part of the linux-next scan project:
> https://scan.coverity.com/projects/linux-next-weekly-scan
>
> You're getting this email because you were associated with the identified
> lines of code (noted below) that were touched by commits:
>
>   Mon Aug 31 19:10:08 2020 -0400
>     a0922278f83e ("drm/nouveau/kms/nv50-: Refactor and cleanup DP HPD handling")

Hi Kees, this looks like a good idea, but maybe double check the Cc list
generation? I was Cc'd on four mails today that I thought were
irrelevant to me.

Thanks,
Jani.

>
> Coverity reported the following:
>
> *** CID 1527266:  Null pointer dereferences  (REVERSE_INULL)
> drivers/gpu/drm/nouveau/nouveau_dp.c:237 in nouveau_dp_irq()
> 231     	struct nouveau_encoder *outp = find_encoder(connector, DCB_OUTPUT_DP);
> 232     	struct nouveau_drm *drm = nouveau_drm(outp->base.base.dev);
> 233     	struct nv50_mstm *mstm;
> 234     	u64 hpd = 0;
> 235     	int ret;
> 236
> vvv     CID 1527266:  Null pointer dereferences  (REVERSE_INULL)
> vvv     Null-checking "outp" suggests that it may be null, but it has already been dereferenced on all paths leading to the check.
> 237     	if (!outp)
> 238     		return;
> 239
> 240     	mstm = outp->dp.mstm;
> 241     	NV_DEBUG(drm, "service %s\n", connector->name);
> 242
>
> If this is a false positive, please let us know so we can mark it as
> such, or teach the Coverity rules to be smarter. If not, please make
> sure fixes get into linux-next. :) For patches fixing this, please
> include these lines (but double-check the "Fixes" first):
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1527266 ("Null pointer dereferences")
> Fixes: a0922278f83e ("drm/nouveau/kms/nv50-: Refactor and cleanup DP HPD handling")
>
> Thanks for your attention!

-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: coverity-bot <keescook@chromium.org>, Lyude Paul <lyude@redhat.com>
Cc: "Nathan E. Egge" <unlord@xiph.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Karol Herbst <kherbst@redhat.com>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-next@vger.kernel.org,
	Ben Skeggs <bskeggs@redhat.com>, Dave Airlie <airlied@redhat.com>,
	linux-hardening@vger.kernel.org
Subject: Re: Coverity: nouveau_dp_irq(): Null pointer dereferences
Date: Fri, 11 Nov 2022 11:13:17 +0200	[thread overview]
Message-ID: <87iljl6ehe.fsf@intel.com> (raw)
In-Reply-To: <202211100850.7A8DD75@keescook>

On Thu, 10 Nov 2022, coverity-bot <keescook@chromium.org> wrote:
> Hello!
>
> This is an experimental semi-automated report about issues detected by
> Coverity from a scan of next-20221110 as part of the linux-next scan project:
> https://scan.coverity.com/projects/linux-next-weekly-scan
>
> You're getting this email because you were associated with the identified
> lines of code (noted below) that were touched by commits:
>
>   Mon Aug 31 19:10:08 2020 -0400
>     a0922278f83e ("drm/nouveau/kms/nv50-: Refactor and cleanup DP HPD handling")

Hi Kees, this looks like a good idea, but maybe double check the Cc list
generation? I was Cc'd on four mails today that I thought were
irrelevant to me.

Thanks,
Jani.

>
> Coverity reported the following:
>
> *** CID 1527266:  Null pointer dereferences  (REVERSE_INULL)
> drivers/gpu/drm/nouveau/nouveau_dp.c:237 in nouveau_dp_irq()
> 231     	struct nouveau_encoder *outp = find_encoder(connector, DCB_OUTPUT_DP);
> 232     	struct nouveau_drm *drm = nouveau_drm(outp->base.base.dev);
> 233     	struct nv50_mstm *mstm;
> 234     	u64 hpd = 0;
> 235     	int ret;
> 236
> vvv     CID 1527266:  Null pointer dereferences  (REVERSE_INULL)
> vvv     Null-checking "outp" suggests that it may be null, but it has already been dereferenced on all paths leading to the check.
> 237     	if (!outp)
> 238     		return;
> 239
> 240     	mstm = outp->dp.mstm;
> 241     	NV_DEBUG(drm, "service %s\n", connector->name);
> 242
>
> If this is a false positive, please let us know so we can mark it as
> such, or teach the Coverity rules to be smarter. If not, please make
> sure fixes get into linux-next. :) For patches fixing this, please
> include these lines (but double-check the "Fixes" first):
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1527266 ("Null pointer dereferences")
> Fixes: a0922278f83e ("drm/nouveau/kms/nv50-: Refactor and cleanup DP HPD handling")
>
> Thanks for your attention!

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-11-11  9:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 16:50 Coverity: nouveau_dp_irq(): Null pointer dereferences coverity-bot
2022-11-10 16:50 ` coverity-bot
2022-11-10 16:50 ` [Nouveau] " coverity-bot
2022-11-11  9:13 ` Jani Nikula [this message]
2022-11-11  9:13   ` Jani Nikula
2022-11-11  9:13   ` [Nouveau] " Jani Nikula
2022-11-11 19:21   ` Kees Cook
2022-11-11 19:21     ` Kees Cook
2022-11-11 19:21     ` [Nouveau] " Kees Cook
2022-11-11 20:06     ` Karol Herbst
2022-11-11 20:06       ` Karol Herbst
2022-11-11 20:06       ` [Nouveau] " Karol Herbst
2022-11-11 20:16       ` Kees Cook
2022-11-11 20:16         ` Kees Cook
2022-11-11 20:16         ` [Nouveau] " Kees Cook
2022-11-11 20:38         ` Karol Herbst
2022-11-11 20:38           ` Karol Herbst
2022-11-11 20:38           ` [Nouveau] " Karol Herbst
2022-11-14 10:07           ` Jani Nikula
2022-11-14 10:07             ` Jani Nikula
2022-11-14 10:07             ` [Nouveau] " Jani Nikula

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=87iljl6ehe.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=bskeggs@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo@embeddedor.com \
    --cc=imirkin@alum.mit.edu \
    --cc=keescook@chromium.org \
    --cc=kherbst@redhat.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=tzimmermann@suse.de \
    --cc=unlord@xiph.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.