28 Jun
2022
28 Jun
'22
3:14 p.m.
Hi Herbert,
On Tue, Jun 28, 2022 at 02:05:34PM +0200, Jason A. Donenfeld wrote:
Hi again,
On Tue, Jun 28, 2022 at 12:55:57PM +0200, Jason A. Donenfeld wrote:
Oh wait you're checking kthread_should_stop before the schedule call instead of afterwards, that would do it.
Oh, that's a really good observation, thank you!
Wait, no. I already am kthread_should_stop() it afterwards. That "continue" goes to the top of the loop, which checks it in the while() statement. So something else is amiss. I guess I'll investigate.
I worked out a solution for the "larger problem" now. It's a bit involved, but not too bad. I'll post a patch shortly.
Jason