From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH v2 mptcp-net] mptcp: do not warn on bad input from the network
Date: Thu, 3 Jun 2021 17:06:33 -0700 (PDT) [thread overview]
Message-ID: <414ccd-a370-e7a7-c753-a3327b60347a@linux.intel.com> (raw)
In-Reply-To: <637fc17e2c0f833e820f7f8097fdc1212b4c968f.1622719886.git.pabeni@redhat.com>
On Thu, 3 Jun 2021, Paolo Abeni wrote:
> warn_bad_map() produces a kernel WARN on bad input coming
> from the network. Use pr_debug() to avoid spamming the system
> log.
>
> Additionally, when the right bound check fails, warn_bad_map() reports
> the wrong ssn value, let's fix it.
>
> Fixes: 648ef4b88673 ("mptcp: Implement MPTCP receive path")
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/107
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> I think we should really abvoid the warn here. Later patches will add
> MIB counters for the relevant event
> ---
> net/mptcp/subflow.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
Thanks for the patch Paolo. Looks good.
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
> diff --git a/net/mptcp/subflow.c b/net/mptcp/subflow.c
> index 5ef31aa16cc1..259f99b61c35 100644
> --- a/net/mptcp/subflow.c
> +++ b/net/mptcp/subflow.c
> @@ -787,10 +787,10 @@ static u64 expand_seq(u64 old_seq, u16 old_data_len, u64 seq)
> return seq | ((old_seq + old_data_len + 1) & GENMASK_ULL(63, 32));
> }
>
> -static void warn_bad_map(struct mptcp_subflow_context *subflow, u32 ssn)
> +static void dbg_bad_map(struct mptcp_subflow_context *subflow, u32 ssn)
> {
> - WARN_ONCE(1, "Bad mapping: ssn=%d map_seq=%d map_data_len=%d",
> - ssn, subflow->map_subflow_seq, subflow->map_data_len);
> + pr_debug("Bad mapping: ssn=%d map_seq=%d map_data_len=%d",
> + ssn, subflow->map_subflow_seq, subflow->map_data_len);
> }
>
> static bool skb_is_fully_mapped(struct sock *ssk, struct sk_buff *skb)
> @@ -815,13 +815,13 @@ static bool validate_mapping(struct sock *ssk, struct sk_buff *skb)
> /* Mapping covers data later in the subflow stream,
> * currently unsupported.
> */
> - warn_bad_map(subflow, ssn);
> + dbg_bad_map(subflow, ssn);
> return false;
> }
> if (unlikely(!before(ssn, subflow->map_subflow_seq +
> subflow->map_data_len))) {
> /* Mapping does covers past subflow data, invalid */
> - warn_bad_map(subflow, ssn + skb->len);
> + dbg_bad_map(subflow, ssn);
> return false;
> }
> return true;
> --
> 2.26.3
>
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2021-06-04 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 11:31 [PATCH v2 mptcp-net] mptcp: do not warn on bad input from the network Paolo Abeni
2021-06-04 0:06 ` Mat Martineau [this message]
2021-06-04 20:07 ` Matthieu Baerts
2021-06-04 20:07 ` Matthieu Baerts
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=414ccd-a370-e7a7-c753-a3327b60347a@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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.