bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tal Lossos <tallossos@gmail.com>
Cc: bpf@vger.kernel.org, yhs@fb.com, kpsingh@kernel.org,
	gilad.reti@gmail.com
Subject: Re: [PATCH bpf-next v2] bpf: Change inode_storage's lookup_elem return value from NULL to -EBADF.
Date: Mon, 08 Mar 2021 16:00:06 +0000	[thread overview]
Message-ID: <161521920691.8334.9768614935730579351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210307120948.61414-1-tallossos@gmail.com>

Hello:

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

On Sun,  7 Mar 2021 14:09:48 +0200 you wrote:
> bpf_fd_inode_storage_lookup_elem returned NULL when getting a bad FD,
> which caused -ENOENT in bpf_map_copy_value.
> EBADF is better than ENOENT for a bad FD behaviour.
> 
> The patch was partially contributed by CyberArk Software, Inc.
> 
> Signed-off-by: Tal Lossos <tallossos@gmail.com>
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpf: Change inode_storage's lookup_elem return value from NULL to -EBADF.
    https://git.kernel.org/bpf/bpf/c/769c18b254ca

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-03-08 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 12:09 [PATCH bpf-next v2] bpf: Change inode_storage's lookup_elem return value from NULL to -EBADF Tal Lossos
2021-03-07 18:18 ` Yonghong Song
2021-03-08 15:07   ` KP Singh
2021-03-08 16:00 ` 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=161521920691.8334.9768614935730579351.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=gilad.reti@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=tallossos@gmail.com \
    --cc=yhs@fb.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).