<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 4, 2013 at 4:57 PM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, 04 Dec 2013 16:45:44 -0800, Vipul Jain said:<br>
<br>
> If you don't mind can you please provide me more insight as what can be<br>
> false alarm I can encounter to move pet inside kernel module?<br>
<br>
</div>The issue isn't false alarms - it's failure to alarm when it should.<br>
<br>
The problem is that it's possible for a kernel to get wedged in such a way that<br>
a kernel thread is still able to feed the watchdog timer on a regular basis,<br>
but userspace is effectively hung and unable to proceed. For example, if an<br>
OOPS happens while a filesystem lock is held, all future userspace references<br>
to that filesystem (and possibly all filesystems of the same type) will hang,<br>
eventually strangling the box while the kernel is still perfectly able to keep<br>
the watchdog working.<br>
<br>
</blockquote></div>Hi Valdis,</div><div class="gmail_extra"><br></div><div class="gmail_extra">I see what you are saying but what if the user process that's feeding the dog gets hung and rest of the system is fine then it will bring the whole system down won't it? I basically want to avoid this?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Regards,</div><div class="gmail_extra">Vipul.</div><div class="gmail_extra"><br></div></div>