public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: LTP List <ltp@lists.linux.it>, automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [PATCH v2 1/2] tst_device: Increase DEV_MIN_SIZE to 300 MB
Date: Thu, 18 Aug 2022 13:16:38 +0200	[thread overview]
Message-ID: <Yv4fllRUrfmdjcgg@pevik> (raw)
In-Reply-To: <Yv4dons8AYcqE9gU@yuki>

> Hi!
> > > Previous default 256 MB was not enough for mkfs.xfs since v5.19.0-rc1
> > > [1] which refuses to create filesystems < 300 MB. Although the
> > > limitation can be workarounded by setting three environment variables,
> > > it's better to increase the variable.

> > > [1]: https://lore.kernel.org/all/164738662491.3191861.15611882856331908607.stgit@magnolia/

> > > Reported-by: Martin Doucha <mdoucha@suse.cz>
> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > ---
> > >  lib/tst_device.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)

> > > diff --git a/lib/tst_device.c b/lib/tst_device.c
> > > index c34cbe6d1..8419b80c3 100644
> > > --- a/lib/tst_device.c
> > > +++ b/lib/tst_device.c
> > > @@ -44,7 +44,7 @@
> > >  #define LOOP_CONTROL_FILE "/dev/loop-control"

> > >  #define DEV_FILE "test_dev.img"
> > > -#define DEV_SIZE_MB 256u
> > > +#define DEV_SIZE_MB 300u

> > Subject is wrong - it is saying DEV_MIN_SIZE

> > It really looks weird that DEV_SIZE_MB < DEV_MIN_SIZE
> > What am I missing?

> The DEV_MIN_SIZE macro is used in a LTP test library API test that
> checks that test can override minial device size so it has to be greater
> than DEV_SIZE_MB which is the size used by the test library when
> loopback devices are created.
Tests in lib/newlib_tests/ are tests which test the LTP itself,
maybe use some prefix for these constants would make obvious that it's not part
of the library (i.e. not visible in normal LTP tests).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-08-18 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 10:09 [LTP] [PATCH v2 0/2] Fix mkfs.xfs 300MB min size requirement (v5.19.0) Petr Vorel
2022-08-18 10:09 ` [LTP] [PATCH v2 1/2] tst_device: Increase DEV_MIN_SIZE to 300 MB Petr Vorel
2022-08-18 10:26   ` Amir Goldstein
2022-08-18 11:08     ` Cyril Hrubis
2022-08-18 11:16       ` Petr Vorel [this message]
2022-08-18 10:09 ` [LTP] [PATCH v2 2/2] lib/tests: Increase .dev_min_size Petr Vorel
2022-09-16 21:33 ` [LTP] [PATCH v2 0/2] Fix mkfs.xfs 300MB min size requirement (v5.19.0) Petr Vorel
2022-09-17  2:50   ` Li Wang
2022-09-19  9:25     ` Cyril Hrubis
2022-09-19  9:33       ` Petr Vorel

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=Yv4fllRUrfmdjcgg@pevik \
    --to=pvorel@suse.cz \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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