From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Roi Dayan <roid@nvidia.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nf-next] netfilter: conntrack: udp: fix seen-reply test
Date: Tue, 31 Jan 2023 13:58:46 +0100 [thread overview]
Message-ID: <Y9kQhlJ8FtosZ8LG@salvia> (raw)
In-Reply-To: <2a1a5bb8-a656-bce9-7a17-e7c949cab135@nvidia.com>
On Tue, Jan 31, 2023 at 02:37:21PM +0200, Roi Dayan wrote:
>
>
> On 23/01/2023 18:16, Roi Dayan wrote:
> >
> >
> > On 23/01/2023 14:04, Florian Westphal wrote:
> >> IPS_SEEN_REPLY_BIT is only useful for test_bit() api.
> >>
> >> Fixes: 4883ec512c17 ("netfilter: conntrack: avoid reload of ct->status")
> >> Reported-by: Roi Dayan <roid@nvidia.com>
> >> Signed-off-by: Florian Westphal <fw@strlen.de>
> >> ---
> >> net/netfilter/nf_conntrack_proto_udp.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/net/netfilter/nf_conntrack_proto_udp.c b/net/netfilter/nf_conntrack_proto_udp.c
> >> index 6b9206635b24..0030fbe8885c 100644
> >> --- a/net/netfilter/nf_conntrack_proto_udp.c
> >> +++ b/net/netfilter/nf_conntrack_proto_udp.c
> >> @@ -104,7 +104,7 @@ int nf_conntrack_udp_packet(struct nf_conn *ct,
> >> /* If we've seen traffic both ways, this is some kind of UDP
> >> * stream. Set Assured.
> >> */
> >> - if (status & IPS_SEEN_REPLY_BIT) {
> >> + if (status & IPS_SEEN_REPLY) {
> >> unsigned long extra = timeouts[UDP_CT_UNREPLIED];
> >> bool stream = false;
> >>
> >
> > Reviewed-by: Roi Dayan <roid@nvidia.com>
> >
> > thanks
>
> hi, just pinging. when is this fix going to be merged?
I'll take care of this.
Thanks.
next prev parent reply other threads:[~2023-01-31 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 12:04 [PATCH nf-next] netfilter: conntrack: udp: fix seen-reply test Florian Westphal
2023-01-23 16:16 ` Roi Dayan
2023-01-31 12:37 ` Roi Dayan
2023-01-31 12:58 ` Pablo Neira Ayuso [this message]
2023-02-01 11:17 ` Pablo Neira Ayuso
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=Y9kQhlJ8FtosZ8LG@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=roid@nvidia.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).