From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Florian Westphal <fw@strlen.de>
Cc: Simon Horman <simon.horman@corigine.com>,
netdev@vger.kernel.org, xiyou.wangcong@gmail.com,
jiri@resnulli.us
Subject: Re: [PATCH net 1/3] net/sched: act_ipt: add sanity checks on table name and hook locations
Date: Thu, 8 Jun 2023 12:44:19 -0400 [thread overview]
Message-ID: <CAM0EoM=F0x2mY-RHN9Me2qZav31Z6jwee2_p6fKQDyW8kybaQA@mail.gmail.com> (raw)
In-Reply-To: <20230608135719.GC27126@breakpoint.cc>
On Thu, Jun 8, 2023 at 9:57 AM Florian Westphal <fw@strlen.de> wrote:
>
> Simon Horman <simon.horman@corigine.com> wrote:
> > I think that patches for 'net' usually come with a fixes tag.
> > Likewise for the other patches in this series.
>
> Right, I'll add
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
If we want to be pedantic (not trying to be) that cannot be the
correct Fixes tag since some of these issues are a result of feature
additions to netfilter (post 2.6.12-rc2) . But it's ok to use that
tag.
cheers,
jamal
next prev parent reply other threads:[~2023-06-08 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 14:59 [PATCH net 0/3] net/sched: act_ipt bug fixes Florian Westphal
2023-06-07 14:59 ` [PATCH net 1/3] net/sched: act_ipt: add sanity checks on table name and hook locations Florian Westphal
2023-06-08 10:44 ` Simon Horman
2023-06-08 13:57 ` Florian Westphal
2023-06-08 16:44 ` Jamal Hadi Salim [this message]
2023-06-07 14:59 ` [PATCH net 2/3] net/sched: act_ipt: add sanity checks on skb before calling target Florian Westphal
2023-06-08 10:44 ` Simon Horman
2023-06-07 14:59 ` [PATCH net 3/3] net/sched: act_ipt: zero skb->cb " Florian Westphal
2023-06-08 10:45 ` Simon Horman
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='CAM0EoM=F0x2mY-RHN9Me2qZav31Z6jwee2_p6fKQDyW8kybaQA@mail.gmail.com' \
--to=jhs@mojatatu.com \
--cc=fw@strlen.de \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.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).