public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Joseph Vance Reilly <Joseph.Reilly@uga.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: AF_XDP bug
Date: Tue, 15 Aug 2023 07:59:35 +0700	[thread overview]
Message-ID: <ZNrN95kPtAiwhGO0@debian.me> (raw)
In-Reply-To: <CH2PR02MB701415DEC996810D20D2EB60F117A@CH2PR02MB7014.namprd02.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

On Mon, Aug 14, 2023 at 12:45:57PM +0000, Joseph Vance Reilly wrote:
> Hello,
> 
> My name is Joseph Reilly and I recently created a bug report on the bugzilla page for the linux kernel. This is a bug that causes an IO_PAGEFAULT when receiving high amounts of traffic on an interface running an XDP program. This problem has been observed with a Mellanox networking card and AMD CPU but may also be present in more configurations. The bugzilla report is here: https://bugzilla.kernel.org/show_bug.cgi?id=217712
> 
> For reference, the bug is #217712 in the networking product listed under the component "other"
> 

If you'd like to forward your BZ report to the mailing lists:

* Quote the whole starting thread and on the forward mail, add pointer to
  your attached files on BZ
* Add relevant subsystems and maintainers to recipient list. See MAINTAINERS
  on the root of kernel tree or run `scripts/get_maintainer.pl` script.
  This is important; otherwise you won't get any helpful responses.

I had forwarded your report on [1] as an example.

Thanks.

[1]: https://lore.kernel.org/bpf/e75b57d9-9093-0a22-d53d-e510fd422279@gmail.com/

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-08-15  1:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 12:45 AF_XDP bug Joseph Vance Reilly
2023-08-15  0:59 ` Bagas Sanjaya [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=ZNrN95kPtAiwhGO0@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=Joseph.Reilly@uga.edu \
    --cc=linux-kernel@vger.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