Re: [PATCH v2] livepatch/module: make TAINT_LIVEPATCH module-specific

On Thu, 25 Aug 2016, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with TAINT_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty party is b

Re: [PATCH v2] livepatch/module: make TAINT_LIVEPATCH module-specific

On Thu, 25 Aug 2016, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with TAINT_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty party is b

Re: [PATCH v2] livepatch/module: make TAINT_LIVEPATCH module-specific

On Thu 2016-08-25 10:04:45, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with TAINT_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty part

[PATCH v2] livepatch/module: make TAINT_LIVEPATCH module-specific

There's no reliable way to determine which module tainted the kernel with TAINT_LIVEPATCH. For example, /sys/module//taint doesn't report it. Neither does the "mod -t" command in the crash tool. Make it crystal clear who the guilty party is by associating TAINT_LIVEPATCH with any module which se

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Thu, Aug 25, 2016 at 04:25:15PM +0200, Miroslav Benes wrote: > On Wed, 24 Aug 2016, Josh Poimboeuf wrote: > > > There's no reliable way to determine which module tainted the kernel > > with CONFIG_LIVEPATCH. For example, /sys/module//taint > > doesn't report it. Neither does the "mod -t" comm

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Thu, 25 Aug 2016, Josh Poimboeuf wrote: > On Thu, Aug 25, 2016 at 04:25:15PM +0200, Miroslav Benes wrote: > > On Wed, 24 Aug 2016, Josh Poimboeuf wrote: > > > > > There's no reliable way to determine which module tainted the kernel > > > with CONFIG_LIVEPATCH. For example, /sys/module//taint

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Wed, 24 Aug 2016, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty party is

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Thu, Aug 25, 2016 at 09:46:06AM +0200, Petr Mladek wrote: > Hi, > > I have spent some time to understand the change. I hope that the > comments below would help others. > > On Wed 2016-08-24 16:33:00, Josh Poimboeuf wrote: > > There's no reliable way to determine which module tainted the kerne

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

Jiri Kosina writes: > On Wed, 24 Aug 2016, Josh Poimboeuf wrote: > >> There's no reliable way to determine which module tainted the kernel >> with CONFIG_LIVEPATCH. For example, /sys/module//taint >> doesn't report it. Neither does the "mod -t" command in the crash tool. >> >> Make it crystal c

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

Hi, I have spent some time to understand the change. I hope that the comments below would help others. On Wed 2016-08-24 16:33:00, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module//taint > doesn't repor

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Wed, Aug 24, 2016 at 04:33:00PM -0500, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Josh-Poimboeuf/livepatch-module-make-TAINT_LIVEPATCH-module-specific/20160825-053847 base: ht

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Wed, 24 Aug 2016, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty party is

Re: livepatch/module: make TAINT_LIVEPATCH module-specific

+++ Josh Poimboeuf [24/08/16 16:33 -0500]: There's no reliable way to determine which module tainted the kernel with CONFIG_LIVEPATCH. For example, /sys/module//taint doesn't report it. Neither does the "mod -t" command in the crash tool. Make it crystal clear who the guilty party is by conver

Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

On Wed, Aug 24, 2016 at 04:33:00PM -0500, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who

[PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific

There's no reliable way to determine which module tainted the kernel with CONFIG_LIVEPATCH. For example, /sys/module//taint doesn't report it. Neither does the "mod -t" command in the crash tool. Make it crystal clear who the guilty party is by converting CONFIG_LIVEPATCH to a module taint flag.