From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: valis <sec@valis.email>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, xiyou.wangcong@gmail.com,
jiri@resnulli.us, davem@davemloft.net, edumazet@google.com,
pctammela@mojatatu.com, victor@mojatatu.com, ramdhan@starlabs.sg,
billy@starlabs.sg,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH net 0/3] net/sched Bind logic fixes for cls_fw, cls_u32 and cls_route
Date: Wed, 26 Jul 2023 08:25:14 -0700 [thread overview]
Message-ID: <20230726082514.63ba446d@kernel.org> (raw)
In-Reply-To: <CAM0EoM=LiL-exVpP-sTT8rh=odFhu_eYY=ob6yMxQP5MGTU00w@mail.gmail.com>
On Wed, 26 Jul 2023 09:59:02 -0400 Jamal Hadi Salim wrote:
> > If Jamal or anyone else feels like they can vouch for the provenance
> > of the code, I think that may be the best compromise.
>
> I am more than happy to add my SoB - these are real issues being fixed
> and this is not the first time that Valis identified and helped
> resolve legit issues in tc.
Great! Please repost with your signoffs.
prev parent reply other threads:[~2023-07-26 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 17:48 [PATCH net 0/3] net/sched Bind logic fixes for cls_fw, cls_u32 and cls_route valis
2023-07-21 17:48 ` [PATCH net 1/3] net/sched: cls_u32: No longer copy tcf_result on update to avoid use-after-free valis
2023-07-21 18:04 ` M A Ramdhan
2023-07-21 18:58 ` Pedro Tammela
2023-07-21 20:38 ` M A Ramdhan
2023-07-21 19:55 ` Jamal Hadi Salim
2023-07-21 17:48 ` [PATCH net 2/3] net/sched: cls_fw: " valis
2023-07-21 17:48 ` [PATCH net 3/3] net/sched: cls_route: " valis
2023-07-21 19:00 ` [PATCH net 0/3] net/sched Bind logic fixes for cls_fw, cls_u32 and cls_route Pedro Tammela
2023-07-21 19:56 ` Jamal Hadi Salim
2023-07-23 7:25 ` M A Ramdhan
2023-07-25 12:57 ` Paolo Abeni
2023-07-25 19:05 ` valis
2023-07-25 20:09 ` Jakub Kicinski
2023-07-25 21:36 ` valis
2023-07-25 22:03 ` Jakub Kicinski
2023-07-26 4:07 ` Greg Kroah-Hartman
2023-07-26 13:59 ` Jamal Hadi Salim
2023-07-26 15:25 ` Jakub Kicinski [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=20230726082514.63ba446d@kernel.org \
--to=kuba@kernel.org \
--cc=billy@starlabs.sg \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=ramdhan@starlabs.sg \
--cc=sec@valis.email \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.