Re: [PATCH mptcp-net 0/2] mptcp: replace lock_sock_fast with sleepable lock

[gang.yan@linux.dev]

April 27, 2026 at 11:04 PM, "Matthieu Baerts" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%22%20%3Cmatttbe%40kernel.org%3E > wrote:


> 
> Hi Gang,
> 
> On 22/04/2026 11:19, Gang Yan wrote:
> 
> > 
> > From: Gang Yan <yangang@kylinos.cn>
> >  
> >  Hi Matt,
> > 
> (I'm not the only one here, anybody is very welcome to review the
> patches: if you put only my name, other people will not tend to review
> your patches ;) )
Got it, thanks for your reminder.

> 
> > 
> > I make some progress about the issue sashiko mentioned in:
> >  https://sashiko.dev/#/patchset/20260420093343.16443-1-gang.yan@linux.dev
> >  
> >  The problem does exist,though the trigger conditions seem quite strict.
> >  
> >  asdasda shjaksdjh askjd hjklajsdhfj klasjd aklshd kljasldkj akjlsd klklk
> > 
> (Not sure what this ↑ means)

The random garbled content was caused by accidental typing due to my local
environment issue, which was a careless mistake on my part.

Recently, I’m actively learning and getting familiar with the b4 tool. 
I will standardize my patch submission process and ensure that such messy content
and irrelevant errors will not appear in future patches.

Thanks
Gang

> 
> I only applied patch 1/2:
> 
> New patches for t/upstream-net and t/upstream:
> - 38bf59aed203: mptcp: fix scheduling with atomic in timestamp sockopt
> - Results: 6d491ca82084..1198f2f92b39 (export-net)
> - Results: 2f9eb2a59db0..3c2b57fddf87 (export)
> 
> Tests are now in progress:
> 
> - export-net:
> https://github.com/multipath-tcp/mptcp_net-next/commit/42417392e5ff4cba41b6b585233d57bd9102f2da/checks
> - export:
> https://github.com/multipath-tcp/mptcp_net-next/commit/9b2ff7d1da660653ed4d10f0888aa499b7988b54/checks
> 
> Cheers,
> Matt
> -- 
> Sponsored by the NGI0 Core fund.
>