Hi Dan/Andrew/Jan,
"Aneesh Kumar K.V" writes:
> Architectures like ppc64 use the deposited page table to store hardware
> page table slot information. Make sure we deposit a page table when
> using zero page at the pmd level for hash.
>
> Without this we hit
>
> Unable to handle kernel paging
The original message was received at Wed, 13 Mar 2019 11:53:14 +0800
from lists.01.org [84.31.171.236]
- The following addresses had permanent fatal errors -
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
linux-nvdimm@lists.01.org
¸½ ¼þ ÄÚ ÈÝ Çë Äú ²é ÔÄ
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Tue, 2019-03-12 at 14:37 -0700, Dan Williams wrote:
> The dynamic-debug statements for command payload output only get
> emitted
> when the command is not ND_CMD_CALL. Move the output payload dumping
> ahead of the early return path for ND_CMD_CALL.
>
> Fixes: 31eca76ba2fc9 ("...whitelisted
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/fsdax-for-5.1
...to receive a small collection of cleanups and an Xarray fix for
v5.1-rc1. It has soaked in -next without issue, although the Xarray
fix was recently re-flowed to fix up a tracepoint
On Tue, 2019-03-12 at 15:07 -0700, Andrew Morton wrote:
> On Wed, 5 Dec 2018 21:42:47 +0100 Michal Hocko wrote:
>
> > > I got your explanation. However Andrew had already applied the patches
> > > and I had some outstanding issues in them that needed to be addressed.
> > > So I thought it best
On Wed, 5 Dec 2018 21:42:47 +0100 Michal Hocko wrote:
> > I got your explanation. However Andrew had already applied the patches
> > and I had some outstanding issues in them that needed to be addressed.
> > So I thought it best to send out this set of patches with those fixes
> > before the
The dynamic-debug statements for command payload output only get emitted
when the command is not ND_CMD_CALL. Move the output payload dumping
ahead of the early return path for ND_CMD_CALL.
Fixes: 31eca76ba2fc9 ("...whitelisted dimm command marshaling mechanism")
Reported-by: Vishal Verma
Hi Guys,
"> It's limited to xfs, no failure on ext4 to date", this is incorrect. I have
been able to reproduce this issue with ext4. In order to do that, I need to run
the full test (on both pmems in the system) and not the half test (only 1 pmem)
that I use for inducing the hang under XFS.
In case kmemdup fails, the fix goes to blk_err to avoid NULL
pointer dereference
Signed-off-by: Kangjie Lu
---
drivers/nvdimm/namespace_devs.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/nvdimm/namespace_devs.c b/drivers/nvdimm/namespace_devs.c
index
10 matches
Mail list logo