public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [RFC PATCH] fallocate05: increase the fallocate and defallocate size
Date: Fri, 24 Sep 2021 22:16:25 -0400	[thread overview]
Message-ID: <20210925021625.GC4029248@maple.netwinder.org> (raw)
In-Reply-To: <20210924202601.GB4029248@maple.netwinder.org>

On Fri, Sep 24, 2021 at 04:26:01PM -0400, Ralph Siemsen wrote:

>Well, this is certainly possible, although there are no intentional 
>changes in the kernel (esp filesystems). Only drivers for flash, 
>architecture support, etc. One possible option would be to try testing 
>a generic ARM kernel under qemu, to see if we can reproduce it there.

I am able to reproduce the behaviour under qemu ARM emulation. The 
kernel in this case is 5.4.142 -- a vanilla version directly from the 
stable 5.4.y kernel series.

I repeated tests 1) and 2) in this environment, getting essentially the 
same result as on the actual hardware:

1) LTP 20210524, fallocate05 test passes.

2) Latest git 443cbc1039f, fallocate05 seems to trigger OOM while
    filling up the tmpfs. Here is the complete log:
    https://gist.github.com/rfs613/f58bd803d1119bf30eb723aef4abf1f5
    The tmpfs test begins on line 759

It's getting late so I won't try the other tests right now, but can do 
so later if desired.

Regards,
Ralph

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

  reply	other threads:[~2021-09-25  2:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 10:46 [LTP] [RFC PATCH] fallocate05: increase the fallocate and defallocate size Li Wang
2021-09-07  2:40 ` Li Wang
2021-09-07  2:40   ` Li Wang
2021-09-07  8:00   ` Jan Stancek
2021-09-07  8:00     ` Jan Stancek
2021-09-08  1:21     ` Li Wang
2021-09-08  1:21       ` Li Wang
2021-09-21 20:33 ` Ralph Siemsen
2021-09-22  5:03   ` Li Wang
2021-09-22  8:21     ` Cyril Hrubis
2021-09-22  9:53       ` Li Wang
2021-09-22  9:56         ` Cyril Hrubis
2021-09-22 10:34           ` Li Wang
2021-09-22 14:32             ` Cyril Hrubis
2021-09-22 16:52               ` Ralph Siemsen
2021-09-23  3:00                 ` Li Wang
2021-09-23  6:29                   ` Li Wang
2021-09-23 13:09                     ` Cyril Hrubis
2021-09-24  4:27                       ` Li Wang
2021-09-23 14:33                 ` Cyril Hrubis
2021-09-24  1:49                   ` Ralph Siemsen
2021-09-24  4:18                     ` Li Wang
2021-09-24 15:11                       ` Ralph Siemsen
2021-09-24 18:26                         ` Cyril Hrubis
2021-09-24 20:26                           ` Ralph Siemsen
2021-09-25  2:16                             ` Ralph Siemsen [this message]
2021-09-26  7:17                             ` Li Wang
2021-09-26  7:40                               ` Li Wang
2021-09-26  7:39                           ` Li Wang
2021-09-27  1:37                             ` Ralph Siemsen
2021-09-24  6:49                   ` Li Wang
2021-09-24  9:33                     ` Cyril Hrubis
2021-09-23  6:39       ` Li Wang
2021-09-23 13:10         ` Cyril Hrubis

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=20210925021625.GC4029248@maple.netwinder.org \
    --to=ralph.siemsen@linaro.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