public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Ido Schimmel <idosch@nvidia•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
	pabeni@redhat•com, edumazet@google•com, petrm@nvidia•com,
	jie2x.zhou@intel•com, mlxsw@nvidia•com
Subject: Re: [PATCH net] netdevsim: Fix hwstats debugfs file permissions
Date: Tue, 20 Sep 2022 01:00:15 +0000	[thread overview]
Message-ID: <166363561560.18776.8219751409513328097.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220909153830.3732504-1-idosch@nvidia.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:

On Fri,  9 Sep 2022 18:38:30 +0300 you wrote:
> The hwstats debugfs files are only writeable, but they are created with
> read and write permissions, causing certain selftests to fail [1].
> 
> Fix by creating the files with write permission only.
> 
> [1]
>  # ./test_offload.py
>  Test destruction of generic XDP...
>  Traceback (most recent call last):
>    File "/home/idosch/code/linux/tools/testing/selftests/bpf/./test_offload.py", line 810, in <module>
>      simdev = NetdevSimDev()
>  [...]
>  Exception: Command failed: cat /sys/kernel/debug/netdevsim/netdevsim0//ports/0/dev/hwstats/l3/disable_ifindex
> 
> [...]

Here is the summary with links:
  - [net] netdevsim: Fix hwstats debugfs file permissions
    https://git.kernel.org/netdev/net/c/34513ada53eb

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



      parent reply	other threads:[~2022-09-20  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 15:38 [PATCH net] netdevsim: Fix hwstats debugfs file permissions Ido Schimmel
2022-09-12  8:57 ` Petr Machata
2022-09-20  1: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=166363561560.18776.8219751409513328097.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=idosch@nvidia$(echo .)com \
    --cc=jie2x.zhou@intel$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=mlxsw@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=petrm@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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