On 10/12/23 9:43 PM, Alexandra Winter wrote:
The subject of the thread says 'smc-r', but some of the changes affect smc-d alike,
don't they?
Yes, sorry for this mistake, it should be bugfix for smc.
On 11.10.23 09:33, D. Wythe wrote:
From: "D. Wythe" <alibuda@xxxxxxxxxxxxxxxxx>
This patches contains bugfix following:
1. hung state
2. sock leak
3. potential panic
I may be helpful for the reviewers, when you point out, which patch fixes which problem.
Were they all found by code reviews?
Or did some occur in real life? If so, then what were the symptoms?
A description of the symptoms is helpful for somebody who is debugging and wants to check
whether the issue was already fixed upstream.
Hi Alexandra,
Except for the issue with the barrier, which was feedback from the
review, all other issues have actually occurred in our environment
and have been verified through internal testing. However, most of these
issues are caused by reference leakage rather than panic, so it is
difficult to provide a
representative phenomenon. But what you said is do necessary, so I will
post some phenomena in the next version, such as
lsmod | grep smc
or
smcss - a
In that case, we can found the issues of reference residue or the
connection residue. Hope it can be helpful to you.
Thanks,
D. Wythe
