lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <a5eaedfa0804080915va0aa272ye2869b904a86dc69@mail.gmail.com>
Date:	Tue, 8 Apr 2008 21:45:14 +0530
From:	"Veda N" <veda74@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: kernel thread does not wakeup

Hi,
   I am having a driver during initialisation i create a thread using
kthread_run.
   As soon as the initialisation function is complete. I start getting
interrupts.

   The kernel thread waits on a struct completion using
wait_for_completion_interruptib
le  function.
   Whenever an interrupt arrives i call the function complete to
wakeup the thread.
   For somereason the kernel thread does not awake.
   I have put some debug prints to see if the address struct
completion is the same.
   It gives the address to be same.

   I dont know why the kernel thread does not wakeup.

   Is there any restriction of using kernel threads during the linux
kernel bootup?.

  What i am trying to say is can i make a thread go sleep during linux
kernel bootup
  and wake it up during kernel bootup upon occurance of an interrupt.

Regards,
vedan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ