Re: suspicious behaviour in pcwd driver.

Hi!


>  > 2. that printk will never hit the logs, so the admin will just find
>  > a powered off box with no idea what happened.
>  > Should we at least sync block devices before doing the power off ?
> 
> AFAICS, this is still a problem with kernel_power_off() though ?
> 

Look at how acpi does this; we probably want to trigger clean shutdown.
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- suspicious behaviour in pcwd driver.
  - From: Dave Jones <[email protected]>
- Re: suspicious behaviour in pcwd driver.
  - From: Dave Jones <[email protected]>

Prev by Date: Re: [patch] IBM HDAPS accelerometer driver.
Next by Date: Re: [PATCH] fix whitespace handling on sysfs attributes
Previous by thread: Re: suspicious behaviour in pcwd driver.
Next by thread: Re: suspicious behaviour in pcwd driver.
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind]