On 2015/1/22 17:15, Miroslav Benes wrote: > On Thu, 22 Jan 2015, Li Bin wrote: > >> On 2015/1/21 17:07, Li Bin wrote: >>> This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17. >>> >>> The method that only allowing the topmost patch on the stack to be >>> enabled or disabled is unreasonable. Such as the following case: >>> >>> - do live patch1 >>> - disable patch1 >>> - do live patch2 //error >>> >>> Now, we will never be able to do new live patch unless disabing the >>> patch1 although there is no dependencies. >>> >> >> Correct the log: >> ... unless disabling the patch1 although ... --> >> ... unless enabling the patch1 firstly although ... > > Yes, but in such situation you can unregister patch1 and proceed with new > live patch. No problem. As Jiri has already written. Or are we missing > something? > Ok, that is before process with new live patch we must unregister the disabled patch1 previously. Is there need some message to avoid confusing the user? Thanks, Li Bin > Regards, > -- > Miroslav Benes > SUSE Labs > -- > To unsubscribe from this list: send the line "unsubscribe live-patching" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > . > -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
