From: Alison Schofield <alison.schofield@intel.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Subject: Re: [ndctl PATCH] cxl/test: use max_available_extent in cxl-destroy-region
Date: Mon, 22 Apr 2024 13:43:53 -0700 [thread overview]
Message-ID: <ZibMCY8G4rDb48Bp@aschofie-mobl2> (raw)
In-Reply-To: <7a8214e2f84e333784cf9e7ecd851ccbbb93f3ec.camel@intel.com>
On Mon, Apr 22, 2024 at 10:07:58AM -0700, Vishal Verma wrote:
> On Wed, 2024-03-27 at 11:46 -0700, alison.schofield@intel.com wrote:
> > From: Alison Schofield <alison.schofield@intel.com>
> >
> > Using .size in decoder selection can lead to a set_size failure with
> > these error messages:
> >
> > cxl region: create_region: region8: set_size failed: Numerical result out of range
> >
> > [] cxl_core:alloc_hpa:555: cxl region8: HPA allocation error (-34) for size:0x0000000020000000 in CXL Window 0 [mem 0xf010000000-0xf04fffffff flags 0x200]
> >
> > Use max_available_extent for decoder selection instead.
> >
> > The test overlooked the region creation failure because it used a
> > not 'null' comparison which always succeeds. Use the ! comparator
> > after create-region and for the ramsize check so that the test fails
> > or continues as expected.
> >
> > Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> > ---
> > test/cxl-destroy-region.sh | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/test/cxl-destroy-region.sh b/test/cxl-destroy-region.sh
> > index cf0a46d6ba58..167fcc4a7ff9 100644
> > --- a/test/cxl-destroy-region.sh
> > +++ b/test/cxl-destroy-region.sh
> > @@ -22,7 +22,7 @@ check_destroy_ram()
> > decoder=$2
> >
> > region="$("$CXL" create-region -d "$decoder" -m "$mem" | jq -r ".region")"
> > - if [ "$region" == "null" ]; then
> > + if [[ ! $region ]]; then
> > err "$LINENO"
> > fi
> > "$CXL" enable-region "$region"
> > @@ -38,7 +38,7 @@ check_destroy_devdax()
> > decoder=$2
> >
> > region="$("$CXL" create-region -d "$decoder" -m "$mem" | jq -r ".region")"
> > - if [ "$region" == "null" ]; then
> > + if [[ ! $region ]]; then
>
> While these ! $region changes are correct (because cxl create-region)
> doesn't output any json if creation fails)..
>
> > err "$LINENO"
> > fi
> > "$CXL" enable-region "$region"
> > @@ -55,14 +55,14 @@ check_destroy_devdax()
> > readarray -t mems < <("$CXL" list -b "$CXL_TEST_BUS" -M | jq -r '.[].memdev')
> > for mem in "${mems[@]}"; do
> > ramsize="$("$CXL" list -m "$mem" | jq -r '.[].ram_size')"
> > - if [[ $ramsize == "null" ]]; then
> > + if [[ ! $ramsize ]]; then
>
> .. I think this check needs to check for both empty and "null" - a
> memdev that doesn't have ram_size but otherwise emits valid json will
> result in "null" here. e.g.:
>
> $ echo "" | jq -r ".region"
>
> $ echo "{ }" | jq -r ".region"
> null
>
> So this probably wants to be:
>
> if [[ $ramsize == "null" || ! $ram_size ]]; then
> ...
>
I see now! Thanks Vishal.
-- Alison
prev parent reply other threads:[~2024-04-22 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 18:46 [ndctl PATCH] cxl/test: use max_available_extent in cxl-destroy-region alison.schofield
2024-04-22 17:07 ` Verma, Vishal L
2024-04-22 20:43 ` Alison Schofield [this message]
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=ZibMCY8G4rDb48Bp@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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).