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]
Date:	Mon, 16 Nov 2015 22:59:30 +0100 (CET)
From:	Jiri Kosina <jikos@...nel.org>
To:	Chris J Arges <chris.j.arges@...onical.com>
cc:	live-patching@...r.kernel.org, jpoimboe@...hat.com,
	sjenning@...hat.com, Vojtech Pavlik <vojtech@...e.com>,
	pmladek@...e.com, jeyu@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3 v7] livepatch: add old_sympos as disambiguator field
 to klp_func

On Mon, 16 Nov 2015, Chris J Arges wrote:

> In cases of duplicate symbols, old_sympos will be used to disambiguate
> instead of old_addr. By default old_sympos will be 0, and patching will
> only succeed if the symbol is unique. Specifying a positive value will
> ensure that occurrence of the symbol in kallsyms for the patched object
> will be used for patching if it is valid.
> 
> In addition, make old_addr an internal structure field not to be specified
> by the user. Finally, remove klp_find_verify_func_addr as it can be
> replaced by klp_find_object_symbol directly.
> 
> Support for symbol position disambiguation for relocations is added in the
> next patch in this series.

Chris,

I am sorry to repeat myself, but the changelog is quite verbose with 
respect to "what is being done", but it doesn't contain any information 
whatsoever with respect to "why is this an improvement over current 
state", IOW why we are changing the status quo at all.

This absolutely has to be present in the changelog.

Thanks,

-- 
Jiri Kosina
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ