From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Sachin Sant <sachinp@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: harish@linux.ibm.com
Subject: Re: [-merge] BUG followed by oops running ndctl tests
Date: Sat, 16 Nov 2019 00:25:14 +0530 [thread overview]
Message-ID: <86aee55a-3968-cf0d-6030-cbc6e63fddc9@linux.ibm.com> (raw)
In-Reply-To: <B0EBF64C-3B57-4716-BAAF-CBC4CBDF5FBC@linux.vnet.ibm.com>
On 11/15/19 11:36 AM, Sachin Sant wrote:
> Following Oops is seen on latest (commit 3b4852888d) powerpc merge branch
> code while running ndctl (test_namespace) tests
>
> 85c5b0984e was good.
>
Are the namespace size created with size that is multiple of 16M size?
Wondering whether this is related to
https://patchwork.kernel.org/patch/11215049/
-aneesh
next prev parent reply other threads:[~2019-11-15 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 6:06 [-merge] BUG followed by oops running ndctl tests Sachin Sant
2019-11-15 12:04 ` Michael Ellerman
2019-11-15 18:55 ` Aneesh Kumar K.V [this message]
2019-11-19 5:24 ` Sachin Sant
2019-11-29 7:57 ` Aneesh Kumar K.V
2019-12-03 8:58 ` Aneesh Kumar K.V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86aee55a-3968-cf0d-6030-cbc6e63fddc9@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=harish@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).