All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: YANG LI <abaci-bugfix@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	ljp@linux.ibm.com, drt@linux.ibm.com, kuba@kernel.org,
	sukadev@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net, paulus@samba.org
Subject: Re: [PATCH] ibmvnic: fix: NULL pointer dereference.
Date: Mon, 04 Jan 2021 21:30:08 +0000	[thread overview]
Message-ID: <160979580868.407.15154718207027980381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1609312994-121032-1-git-send-email-abaci-bugfix@linux.alibaba.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Wed, 30 Dec 2020 15:23:14 +0800 you wrote:
> The error is due to dereference a null pointer in function
> reset_one_sub_crq_queue():
> 
> if (!scrq) {
>     netdev_dbg(adapter->netdev,
>                "Invalid scrq reset. irq (%d) or msgs(%p).\n",
> 		scrq->irq, scrq->msgs);
> 		return -EINVAL;
> }
> 
> [...]

Here is the summary with links:
  - ibmvnic: fix: NULL pointer dereference.
    https://git.kernel.org/netdev/net/c/862aecbd9569

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: YANG LI <abaci-bugfix@linux.alibaba.com>
Cc: davem@davemloft.net, kuba@kernel.org, drt@linux.ibm.com,
	ljp@linux.ibm.com, sukadev@linux.ibm.com, mpe@ellerman.id.au,
	benh@kernel.crashing.org, paulus@samba.org,
	netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ibmvnic: fix: NULL pointer dereference.
Date: Mon, 04 Jan 2021 21:30:08 +0000	[thread overview]
Message-ID: <160979580868.407.15154718207027980381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1609312994-121032-1-git-send-email-abaci-bugfix@linux.alibaba.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Wed, 30 Dec 2020 15:23:14 +0800 you wrote:
> The error is due to dereference a null pointer in function
> reset_one_sub_crq_queue():
> 
> if (!scrq) {
>     netdev_dbg(adapter->netdev,
>                "Invalid scrq reset. irq (%d) or msgs(%p).\n",
> 		scrq->irq, scrq->msgs);
> 		return -EINVAL;
> }
> 
> [...]

Here is the summary with links:
  - ibmvnic: fix: NULL pointer dereference.
    https://git.kernel.org/netdev/net/c/862aecbd9569

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2021-01-04 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30  7:23 [PATCH] ibmvnic: fix: NULL pointer dereference YANG LI
2020-12-30  7:23 ` YANG LI
2020-12-30 13:48 ` Michal Suchánek
2020-12-30 13:48   ` Michal Suchánek
2020-12-30 22:00 ` Lijun Pan
2020-12-30 22:00   ` Lijun Pan
2021-01-04 21:30 ` patchwork-bot+netdevbpf [this message]
2021-01-04 21:30   ` patchwork-bot+netdevbpf

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=160979580868.407.15154718207027980381.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=abaci-bugfix@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=drt@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ljp@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sukadev@linux.ibm.com \
    /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.