linux-kernel - Re: [PATCH 1/2] livepatch: Revert "livepatch: enforce patch stacking semantics"

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1501221013580.24802@pobox.suse.cz>
Date:	Thu, 22 Jan 2015 10:15:04 +0100 (CET)
From:	Miroslav Benes <mbenes@...e.cz>
To:	Li Bin <huawei.libin@...wei.com>
cc:	Josh Poimboeuf <jpoimboe@...hat.com>,
	Seth Jennings <sjenning@...hat.com>,
	Jiri Kosina <jkosina@...e.cz>,
	Vojtech Pavlik <vojtech@...e.cz>, Jiri Slaby <jslaby@...e.cz>,
	live-patching@...r.kernel.org, linux-kernel@...r.kernel.org,
	lizefan@...wei.com, guohanjun@...wei.com, zhangdianfang@...wei.com,
	xiexiuqi@...wei.com
Subject: Re: [PATCH 1/2] livepatch: Revert "livepatch: enforce patch stacking
 semantics"

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?

Regards,
--
Miroslav Benes
SUSE Labs
--
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/