All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs: sleeping function called from invalid context
Date: Mon, 24 Feb 2020 16:56:00 -0500	[thread overview]
Message-ID: <20200224215600.GB6688@mit.edu> (raw)
In-Reply-To: <CAL3q7H4-edAwsSc0Z+dYVzphm6-D1BjvToywL0A2v6unsCCtyg@mail.gmail.com>

On Mon, Feb 24, 2020 at 10:14:06AM +0000, Filipe Manana wrote:
> We do have some tests that fail in any kernel release so far. Some
> because the corresponding fixes are not yet merged or some fail often
> due to known problems.
> Looking at your list of failure, I see some that shouldn't be failing
> like btrfs/053.

I've sent you the compressed tarfile with the test artifacts under
separate cover.  The files that you'll probably want to look at first
are ./runtests.log and ./syslog.  The xfstests results artifacts will
be in ./btrfs/results-default/.

If you have a wiki page or some other pointer of what tests that you
expect to fail, I can put them into a btrfs-specific or file system
configuration specific exclude file.  For example, see [1] and [2].

[1] https://github.com/tytso/xfstests-bld/blob/master/kvm-xfstests/test-appliance/files/root/fs/ext4/exclude
[2] https://github.com/tytso/xfstests-bld/blob/master/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc.exclude

I'm planning on running btrfs and xfs tests more frequently to support
some $WORK initiatives.  So if there are tests which are known
failures that would be good for me to suppress, and if there are some
file system configurations that would be useful for me to run, please
let me know and I'm happy to set them so that gce-xfstests and
kvm-xfstests can better test btrfs.

Also, I assume you do have some btrfs developers who are regularly
running xfstests, so I don't know how helpful this would be to you,
but given that I'm going to be running the tests *anyway*, if it would
be helpful for me to forward test results to you, or to only send you
a note when test regressions show up, I'm happy to do that.

Cheers,

					- Ted

  reply	other threads:[~2020-02-24 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 23:42 btrfs: sleeping function called from invalid context Theodore Y. Ts'o
2020-02-24  0:28 ` Nikolay Borisov
2020-02-24  6:46   ` Theodore Y. Ts'o
2020-02-24 10:14     ` Filipe Manana
2020-02-24 21:56       ` Theodore Y. Ts'o [this message]
2020-02-25  9:36         ` Filipe Manana
2020-02-24 10:11   ` Filipe Manana

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=20200224215600.GB6688@mit.edu \
    --to=tytso@mit.edu \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.