On Tue, 18 Jul 2017 17:11:19 -0300, Martin Galvan said:
> task_struct, it's not clear to me why I didn't get to see the thread
> function printks. If the thread function finished before reaching
> kthread_stop, I should be able to see them, right? The only way I can
> see them is by removing the ca
Still, going back to this issue: even though I made make a mistake and
incorrectly called kthread_stop on a (possibly) non-existent
task_struct, it's not clear to me why I didn't get to see the thread
function printks. If the thread function finished before reaching
kthread_stop, I should be able t
Understood. Thanks a lot!
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Tue, 18 Jul 2017 15:13:08 -0300, Martin Galvan said:
> I thought kthread_create/bind don't actually run the thread function?
> At least that's what the comment says.
It's the wake_up_process() that causes the problem...
> > * If threadfn() may call do_exit() itself, the caller must ensure
>
On Tue, 18 Jul 2017 13:00:11 -0300, Martin Galvan said:
> Hi everyone! I'm doing a bit of testing on the Linux kthread functions, and h
> int function(void *data)
> {
> printk(KERN_DEBUG "CPU: %u\n", smp_processor_id());
>
> do_exit(0); /* Not sure if this is ok */
> }
Note that this will
Hi everyone! I'm doing a bit of testing on the Linux kthread functions, and
have the following module:
#include
#include
#include
#include
#include
#include
MODULE_LICENSE("GPL");
int function(void *data)
{
printk(KERN_DEBUG "CPU: %u\n", smp_processor_id());
do_exit(0); /* Not su
On Thu, 06 Jul 2017 09:23:46 +0200, Massimo Sala said:
> I have an idea about a new sysctl knob. It is under net.ipv4.
Step 0: Identify whether it is even a good idea. TCP/IP is tougher
than you think, especially when you get into congestion control.
Step 0.1: Figure out if your brilliant idea
