netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Xing <kerneljasonxing@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
	pabeni@redhat.com, kuba@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net] tcp: avoid the lookup process failing to get sk in ehash table
Date: Sat, 14 Jan 2023 17:48:02 +0800	[thread overview]
Message-ID: <CAL+tcoBM6YkZgrRHLXXTwZw9rVNfbEk2SeXsz5Zf6ca9LartYA@mail.gmail.com> (raw)
In-Reply-To: <CANn89i+W_1ux=5ixjCdf9LoGuDb6LEJ_XgWCNcYztjPQ0R4L1Q@mail.gmail.com>

On Sat, Jan 14, 2023 at 5:27 PM Eric Dumazet <edumazet@google.com> wrote:
>
> On Sat, Jan 14, 2023 at 3:15 AM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> >
> > So could someone please take some time to help me review the patch?
> > It's not complicated. Thank you from the bottom of my heart in
> > advance.
>
>
> Sure.
>
> Please be patient, and accept the fact that maintainers are
> overwhelmed by mixes of patches and company work.

I felt so sorry. I'm too anxious. Thanks for what you've contributed
to the net module really.

>
> In the meantime, can you double check if the transition from
> established to timewait socket is also covered by your patch ?

Yeah, I'll do that.

Thanks,
Jason

  reply	other threads:[~2023-01-14  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  6:53 [PATCH net] tcp: avoid the lookup process failing to get sk in ehash table Jason Xing
2023-01-14  2:14 ` Jason Xing
2023-01-14  9:26   ` Eric Dumazet
2023-01-14  9:48     ` Jason Xing [this message]
2023-01-14  9:45 ` Eric Dumazet
2023-01-14 12:05   ` Jason Xing
2023-01-14 12:30     ` Eric Dumazet
2023-01-14 12:48       ` Jason Xing

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=CAL+tcoBM6YkZgrRHLXXTwZw9rVNfbEk2SeXsz5Zf6ca9LartYA@mail.gmail.com \
    --to=kerneljasonxing@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kernelxing@tencent.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yoshfuji@linux-ipv6.org \
    /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).