DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Madhuker Mythri <madhuker.mythri@oracle.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>
Subject: Re: [External] : Re: [PATCH] net/tap: Modified TAP BPF program as per the Kernel-version upgrade requirements.
Date: Tue, 16 Jan 2024 08:40:04 -0800	[thread overview]
Message-ID: <20240116084004.146bcf9d@hermes.local> (raw)
In-Reply-To: <SJ0PR10MB47983404BF9E49102AAB9DB997732@SJ0PR10MB4798.namprd10.prod.outlook.com>

On Tue, 16 Jan 2024 05:43:00 +0000
Madhuker Mythri <madhuker.mythri@oracle.com> wrote:

> Hi Stephen,
> 
> Yes, I found that the Kernel we use has more Verification added for safe execution:
> https://blogs.oracle.com/linux/post/bpf-in-depth-the-bpf-bytecode-and-the-bpf-verifier
> 
> Here they mentioned about SKB pointer direct access, math on pointer and array with undefined access is denied on BPF code.
> 
> Thanks,
> Madhuker.

Most of your changes, make sense and should be merged.
But the custom verifier changes do not need to be added.
The DPDK upstream project is not targeted at supporting custom vendor API modifications.

  reply	other threads:[~2024-01-16 16:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 13:48 madhuker.mythri
2024-01-12 16:40 ` Stephen Hemminger
2024-01-12 16:41 ` Stephen Hemminger
2024-01-13 17:50   ` [External] : " Madhuker Mythri
2024-01-13 18:05     ` Stephen Hemminger
2024-01-16 16:43     ` Stephen Hemminger
2024-01-12 16:42 ` Stephen Hemminger
2024-01-13 17:52   ` [External] : " Madhuker Mythri
2024-01-13 18:06     ` Stephen Hemminger
2024-01-16  5:43       ` Madhuker Mythri
2024-01-16 16:40         ` Stephen Hemminger [this message]
2024-01-17  3:25         ` Stephen Hemminger
2024-01-17 16:19           ` Madhuker Mythri
2024-01-12 16:43 ` Stephen Hemminger
2024-01-12 16:46 ` Stephen Hemminger
2024-01-13 17:55   ` [External] : " Madhuker Mythri
2024-01-12 17:53 ` [RFC v3] tap: rework the BPF header parsing Stephen Hemminger
2024-02-07 18:55 ` [PATCH] net/tap: Modified TAP BPF program as per the Kernel-version upgrade requirements Stephen Hemminger

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=20240116084004.146bcf9d@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=madhuker.mythri@oracle.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).