, but
> because modprobe completed, we should be safe, no?
>
> The only "nowait" function we have is load_lp_nowait(), which would let us
> march onward before the livepatch transition may have completed.
And even that one is waiting for the live patch module name appear under
/sys/kernel/livepatch/. This is IMHO acceptable level of paranoia.
Libor
--
Libor Pechacek
SUSE Labs
On Mon 23-04-18 10:43:17, Joe Lawrence wrote:
> On Fri, Apr 20, 2018 at 02:56:05PM +0200, Libor Pechacek wrote:
[...]
> > > +
> > > + # Wait for livepatch transition ...
> > > + local i=0
> > > + while [[ $(cat /sys/kernel/livepatch/"$mod"/t
On Tue 24-04-18 11:50:28, Joe Lawrence wrote:
> On 04/23/2018 10:43 AM, Joe Lawrence wrote:
> > On Fri, Apr 20, 2018 at 02:56:05PM +0200, Libor Pechacek wrote:
> >> On Thu 12-04-18 10:54:31, Joe Lawrence wrote:
> >>> + fi
> >>> + echo "$ret" >
een live patched
> +$MOD_REPLACE: this has been live patched
>
Support for CRIS and Meta was dropped.
Signed-off-by: Libor Pechacek
Fixes: bb6fb6dfcc17 ("metag: Remove arch/metag/")
Fixes: c690eddc2f3b ("CRIS: Drop support for the CRIS port")
Cc: James Hogan
Cc: Jesper Nilsson
Cc: Rob Herring
Cc: Frank Rowand
Cc: Masahiro Yamada
Cc
state does, even more friendly. Possibility to read a
list of available actions would help user space tools identify what is
available in case the list grows in the future.
Libor
--
Libor Pechacek
SUSE Labs
mented in Documentation/ABI/testing/sysfs-kernel-livepatch for
end users.
Libor
--
Libor Pechacek
SUSE Labs
t klp_init(void)
> if (!klp_root_kobj)
> return -ENOMEM;
>
> + ret = sysfs_create_group(klp_root_kobj, &klp_sysfs_group);
> + if (ret) {
> + pr_err("cannot create livepatch attributes in sysfs\n");
> + kobject_put(klp_root_kobj);
> + return ret;
> + }
> +
> return 0;
> }
>
Libor
> --
> 2.12.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe live-patching" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Libor Pechacek
SUSE Labs
While most of the locations where a kernel taint bit is set are accompanied
with a warning message, there are two which set their bits silently. If
the tainting module gets unloaded later on, it is almost impossible to tell
what was the reason for setting the flag.
Signed-off-by: Libor Pechacek
As seen in block/cfq-iosched.c, the parameter name is low_latency.
Signed-off-by: Libor Pechacek
---
Documentation/block/cfq-iosched.txt | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/Documentation/block/cfq-iosched.txt
b/Documentation/block/cfq-iosched.txt
Enabling CONFIG_DEBUG_ATOMIC_SLEEP has shown that some rfcomm functions
acquiring spinlocks call sleeping locks further in the chain. Converting
the offending spinlocks into mutexes makes sleeping safe.
Signed-off-by: Libor Pechacek
---
include/net/bluetooth/rfcomm.h | 6 +++---
net/bluetooth
n to misbehave (as reported by Elo developers).
>
> [v2]
> - allocate the buffer only once (per Oliver)
> - add use_fw_quirk module parameter (per Libor)
Thanks, looks OK to me.
Libor
> Signed-off-by: Jiri Slaby
> Cc: Petr Ostadal
> Cc: Oliver Neukum
> Cc: Vojtech Pavl
t; +
> +
> };
>
> static struct pci_bits piix_enable_bits[] = {
> --
> 1.6.4.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger
13 matches
Mail list logo
