> On 19-Sep-2019, at 9:36 PM, Mark Brown wrote:
>
> Hi all,
>
> Changes since 20190918:
>
> The btrfs-kave tree gained a conflict with Linus' tree which I wasn't
> comfortable resolving so I skipped the tre for today.
>
> The ext4 tree gained a conflict with Linus' tree which I fixed up.
>
> On 24-Mar-2020, at 12:37 PM, Baoquan He wrote:
>
> Hi Sachin,
>
> On 03/24/20 at 11:25am, Sachin Sant wrote:
>> While running ndctl[1] tests against 5.6.0-rc7 following crash is
>> encountered.
>>
>> Bisect leads me to commit d41e2f3bd546
While running ndctl[1] tests against 5.6.0-rc7 following crash is encountered.
Bisect leads me to commit d41e2f3bd546
mm/hotplug: fix hot remove failure in SPARSEMEM|!VMEMMAP case
Reverting this commit helps and the tests complete without any crash.
pmem0: detected capacity change from 0 to
> On 24-Mar-2020, at 2:45 PM, Aneesh Kumar K.V
> wrote:
>
> Sachin Sant writes:
>
>> While running ndctl[1] tests against 5.6.0-rc7 following crash is
>> encountered.
>>
>> Bisect leads me to commit d41e2f3bd546
>> mm/hotplug: fix
> On 20-Oct-2020, at 2:22 PM, Aneesh Kumar K.V
> wrote:
>
> "Aneesh Kumar K.V" writes:
>
>> Hi Christoph,
>>
>> commit 6f42193fd86e ("memremap: don't use a separate devm action for
>> devmap_managed_enable_get") changed the static key updates such that we
>> are now calling
> jump label: negative count!
> WARNING: CPU: 52 PID: 1335 at kernel/jump_label.c:235
> static_key_slow_try_dec+0x88/0xa0
> Modules linked in:
> ….
>
> Cc: Christoph Hellwig
> Cc: Dan Williams
> Cc: Sachin Sant
> Cc: linux-nvdimm@lists.01.org
> Cc: Ira Weiny
ed the
> following.
>
> Signed-off-by: Ralph Campbell
> —
This patch fixes the warning for me.
Tested-by: Sachin Sant
-Sachin
___
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-le...@lists.01.org
