From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
xiyou.wangcong@gmail.com, Davide Caratti <dcaratti@redhat.com>,
netdev@vger.kernel.org, jiri@resnulli.us, pabeni@redhat.com,
wizhao@redhat.com, lucien.xin@gmail.com
Subject: Re: [RFC net-next 2/2] act_mirred: use the backlog for nested calls to mirred ingress
Date: Wed, 11 Jan 2023 11:26:18 -0300 [thread overview]
Message-ID: <Y77HCg39bWRJIPw/@t14s.localdomain> (raw)
In-Reply-To: <CAM0EoMkbgyokMAbvyyjHRCKu42OT1Wp6F_FajtvPQXrCGRZYCw@mail.gmail.com>
On Mon, Jan 09, 2023 at 03:46:10PM -0500, Jamal Hadi Salim wrote:
> On Mon, Jan 9, 2023 at 1:39 PM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Mon, 9 Jan 2023 10:59:49 -0500 Jamal Hadi Salim wrote:
> > > Sorry, I thought it was addressing the issue we discussed last time.
> > > Lets discuss in our monthly meeting.
> >
> > When is your meeting? One could consider this patch as a fix and it
> > looks kinda "obviously correct", so the need for delays and discussions
> > is a bit lost on me.
Long story short, this fix is 3 months old by now. Cong has been very
hesitant to it.
>
> The original issue was discussed in our meetup and the monthly meetup was
> today - where we agreed this patch solves the outstanding issue.
Unfortunatelly Cong didn't attend the mtg, though. Not sure if he is
on PTO or what. We do believe, though, that the patch is now
addressing all his concerns.
Marcelo
>
> No idea what is going on with the stoopid mail client; i gave up on thunderbird
> but possibly the OP used html and this thing is acting in kind. I will double
> check next time...
>
>
> cheers,
> jamal
>
> > Cong, WDYT?
> >
> > Reminder: please don't top post and trim your replies.
prev parent reply other threads:[~2023-01-11 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 18:25 [RFC net-next 1/2] net/sched: act_mirred: better wording on protection against excessive stack growth Davide Caratti
2022-12-20 18:25 ` [RFC net-next 2/2] act_mirred: use the backlog for nested calls to mirred ingress Davide Caratti
2022-12-26 16:03 ` Jamal Hadi Salim
2023-01-05 17:08 ` Marcelo Ricardo Leitner
2023-01-09 15:59 ` Jamal Hadi Salim
2023-01-09 18:39 ` Jakub Kicinski
2023-01-09 20:46 ` Jamal Hadi Salim
2023-01-11 14:26 ` Marcelo Ricardo Leitner [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=Y77HCg39bWRJIPw/@t14s.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wizhao@redhat.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 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).