linux-kernel - Re: [PATCH 2/2] livepatch: disable/enable_patch manners for interdependent patches

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20150122035126.GB12927@treble.redhat.com>
Date:	Wed, 21 Jan 2015 21:51:26 -0600
From:	Josh Poimboeuf <jpoimboe@...hat.com>
To:	Li Bin <huawei.libin@...wei.com>
Cc:	Jiri Kosina <jkosina@...e.cz>, Seth Jennings <sjenning@...hat.com>,
	Vojtech Pavlik <vojtech@...e.cz>, Jiri Slaby <jslaby@...e.cz>,
	Miroslav Benes <mbenes@...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 2/2] livepatch: disable/enable_patch manners for
 interdependent patches

On Thu, Jan 22, 2015 at 08:42:29AM +0800, Li Bin wrote:
> On 2015/1/21 22:08, Jiri Kosina wrote:
> > On Wed, 21 Jan 2015, Li Bin wrote:
> > By this you limit the definition of the patch inter-dependency to just 
> > symbols. But that's not the only way how patches can depend on it other -- 
> > the dependency can be semantical.
> 
> Yes, I agree with you. But I think the other dependencies such as semantical
> dependency should be judged by the user, like reverting a patch from git repository.
> Right?

But with live patching, there are two users: the patch creator (who
creates the patch module) and the end user (who loads it on their
system).

We can assume the patch creator knows what he's doing, but the end user
doesn't always know or care about low level details like patch
dependencies.  The easiest and safest way to protect the end user is the
current approach, which assumes that each patch depends on all
previously applied patches.

-- 
Josh
--
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/