On Tuesday 15 January 2013 17:21:04 joeyli wrote:
於 二，2013-01-15 於 09:37 +0100，Oliver Neukum 提到：
On Tuesday 15 January 2013 13:58:49 Lee, Chun-Yi wrote:
If this new code path is run,
1. we end up with a blocked swap partition 2. we leave an outdated image which would cause file system corruption if the user ever gets it to restore
Is this wise?
Regards Oliver
Did you mean the above situation will happen through the following procedure?
+ user boot system when disabled secure boot + boot to system then trigger S4 suspend -> generate S4 image + user go to BIOS to enable secure boot then boot + software_resume() detected secure boot enabled -> skip S4 image (equals to noresume paramter)
That is a way to get there, but not necessarily the only way.
But, if user use noresume will got the same problem? tracing more...
If the user explicitly tells the kernel to not resume, it his his fault. What we do in that case is not necessarily the right thing to do when the kernel, for a reason not clear to the user, refuses to resume. Regards Oliver -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org