Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1723284
| From | Miroslav Benes <mbenes@suse.cz> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 0/3] livepatch: Introduce force sysfs attribute |
| Date | 2017-08-30 15:00 +0200 |
| Message-ID | <ukaL8-8rd-17@gated-at.bofh.it> (permalink) |
| References | <ucTcl-4sX-5@gated-at.bofh.it> <uf6Ia-7Ci-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH v2 0/3] livepatch: Introduce force sysfs attribute Miroslav Benes <mbenes@suse.cz> - 2017-08-30 15:00 +0200
csiph-web