On Mon, Feb 26, 2024 at 07:33:53PM +0800, qirui wrote: > This issue only occurs in 5.4 LTS versions after LTS 5.4.250 > (inclusive), and this patchset is based on commit > 6e1f54a4985b63bc1b55a09e5e75a974c5d6719b (Linux 5.4.269) Does the bug also exist in mainline? If not, why? -- Josh