From: patchwork-bot+netdevbpf@kernel.org
To: Andrei Gherzan <andrei.gherzan@canonical.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility
Date: Sat, 28 Jan 2023 14:00:17 +0000 [thread overview]
Message-ID: <167491441762.1771.2123081381985522010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230126165548.230453-1-andrei.gherzan@canonical.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 26 Jan 2023 16:55:48 +0000 you wrote:
> "tcpdump" is used to capture traffic in these tests while using a random,
> temporary and not suffixed file for it. This can interfere with apparmor
> configuration where the tool is only allowed to read from files with
> 'known' extensions.
>
> The MINE type application/vnd.tcpdump.pcap was registered with IANA for
> pcap files and .pcap is the extension that is both most common but also
> aligned with standard apparmor configurations. See TCPDUMP(8) for more
> details.
>
> [...]
Here is the summary with links:
- selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility
https://git.kernel.org/netdev/net/c/a6efc42a86c0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-28 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:55 [PATCH] selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility Andrei Gherzan
2023-01-28 14: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=167491441762.1771.2123081381985522010.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrei.gherzan@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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 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).