Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1723284 > unrolled thread

Re: [PATCH v2 0/3] livepatch: Introduce force sysfs attribute

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v2 0/3] livepatch: Introduce force sysfs attribute Miroslav Benes <mbenes@suse.cz> - 2017-08-30 15:00 +0200

#1723284 — Re: [PATCH v2 0/3] livepatch: Introduce force sysfs attribute

On Wed, 16 Aug 2017, Petr Mladek wrote:

> On Thu 2017-08-10 12:48:12, Miroslav Benes wrote:
> > Currently, livepatch gradually migrate the system from an unpatched to a
> > patched state (or vice versa). Each task drops its TIF_PATCH_PENDING
> > itself when crossing the kernel/user space boundary or it is cleared
> > using the stack checking approach. If there is a task which sleeps on a
> > patched function, the whole transition can get stuck indefinitely.
> > 
> > TODO:
> > Now there is a sysfs attribute called "force", which provides two
> > functionalities, "signal" and "force" (previously "unmark"). I haven't
> > managed to come up with better names. Proposals are welcome. On the
> > other hand I do not mind it much.
> 
> What about calling the attribute?
> 
>      transition-speedup
>      transition-urge
> 
> In each case, I would make it more clear that the attribute
> is related to the transition attribute of each patch.

Umm... I don't like that much and those names would definitely confuse me. 
But I'm biased already.

Miroslav

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web