netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vlad Buslov <vladbu@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	dan.carpenter@oracle.com, idosch@nvidia.com
Subject: Re: [PATCH net-next] net: fib_notifier: don't return positive values on fib registration
Date: Thu, 11 Feb 2021 22:50:09 +0000	[thread overview]
Message-ID: <161308380921.17877.5107096834500250763.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210211100759.1156998-1-vladbu@nvidia.com>

Hello:

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

On Thu, 11 Feb 2021 12:07:59 +0200 you wrote:
> The function fib6_walk_continue() cannot return a positive value when
> called from register_fib_notifier(), but ignoring causes static analyzer to
> generate warnings in users of register_fib_notifier() that try to convert
> returned error code to pointer with ERR_PTR(). Handle such case by
> explicitly checking for positive error values and converting them to
> -EINVAL in fib6_tables_dump().
> 
> [...]

Here is the summary with links:
  - [net-next] net: fib_notifier: don't return positive values on fib registration
    https://git.kernel.org/netdev/net-next/c/6f1995523a0f

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



      reply	other threads:[~2021-02-11 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 10:07 [PATCH net-next] net: fib_notifier: don't return positive values on fib registration Vlad Buslov
2021-02-11 22:50 ` patchwork-bot+netdevbpf [this message]

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=161308380921.17877.5107096834500250763.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).