From: Cyril Hrubis <chrubis@suse.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [LTP] [linus:master] [iomap] 219580eea1: ltp.writev07.fail
Date: Fri, 14 Jul 2023 13:53:58 +0200 [thread overview]
Message-ID: <ZLE3Vh5yHq_floF7@yuki> (raw)
In-Reply-To: <CAASaF6xbgSf+X+SF8wLjFrsMA4=XxHti0SXDZQP1ZqdGYp4aUQ@mail.gmail.com>
Hi!
> > > I can't reproduce this on current mainline. Is this a robust failure
> > > or flapping test? Especiall as the FAIL conditions look rather
> > > unrelated.
>
> It's consistently reproducible for me on xfs with HEAD at:
> eb26cbb1a754 ("Merge tag 'platform-drivers-x86-v6.5-2' of
> git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86")
Should be fixed by https://lore.kernel.org/linux-fsdevel/20230714085124.548920-1-hch at lst.de/T/#t
--
Cyril Hrubis
chrubis at suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Matthew Wilcox <willy@infradead.org>,
cluster-devel@redhat.com, Ilya Dryomov <idryomov@gmail.com>,
Miklos Szeredi <mszeredi@redhat.com>, Chao Yu <chao@kernel.org>,
oe-lkp@lists.linux.dev, Al Viro <viro@zeniv.linux.org.uk>,
Jaegeuk Kim <jaegeuk@kernel.org>, Xiubo Li <xiubli@redhat.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
ltp@lists.linux.it, lkp@intel.com, Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>,
Anna Schumaker <anna@kernel.org>,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [LTP] [linus:master] [iomap] 219580eea1: ltp.writev07.fail
Date: Fri, 14 Jul 2023 13:53:58 +0200 [thread overview]
Message-ID: <ZLE3Vh5yHq_floF7@yuki> (raw)
In-Reply-To: <CAASaF6xbgSf+X+SF8wLjFrsMA4=XxHti0SXDZQP1ZqdGYp4aUQ@mail.gmail.com>
Hi!
> > > I can't reproduce this on current mainline. Is this a robust failure
> > > or flapping test? Especiall as the FAIL conditions look rather
> > > unrelated.
>
> It's consistently reproducible for me on xfs with HEAD at:
> eb26cbb1a754 ("Merge tag 'platform-drivers-x86-v6.5-2' of
> git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86")
Should be fixed by https://lore.kernel.org/linux-fsdevel/20230714085124.548920-1-hch@lst.de/T/#t
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Andreas Gruenbacher <agruenba@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Matthew Wilcox <willy@infradead.org>,
cluster-devel@redhat.com, Ilya Dryomov <idryomov@gmail.com>,
Miklos Szeredi <mszeredi@redhat.com>, Chao Yu <chao@kernel.org>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Jaegeuk Kim <jaegeuk@kernel.org>, Xiubo Li <xiubli@redhat.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
ltp@lists.linux.it, lkp@intel.com, Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>,
Anna Schumaker <anna@kernel.org>,
oe-lkp@lists.linux.dev, Andrew Morton <akpm@linux-foundation.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [LTP] [linus:master] [iomap] 219580eea1: ltp.writev07.fail
Date: Fri, 14 Jul 2023 13:53:58 +0200 [thread overview]
Message-ID: <ZLE3Vh5yHq_floF7@yuki> (raw)
In-Reply-To: <CAASaF6xbgSf+X+SF8wLjFrsMA4=XxHti0SXDZQP1ZqdGYp4aUQ@mail.gmail.com>
Hi!
> > > I can't reproduce this on current mainline. Is this a robust failure
> > > or flapping test? Especiall as the FAIL conditions look rather
> > > unrelated.
>
> It's consistently reproducible for me on xfs with HEAD at:
> eb26cbb1a754 ("Merge tag 'platform-drivers-x86-v6.5-2' of
> git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86")
Should be fixed by https://lore.kernel.org/linux-fsdevel/20230714085124.548920-1-hch@lst.de/T/#t
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-07-14 11:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:25 [Cluster-devel] [linus:master] [iomap] 219580eea1: ltp.writev07.fail kernel test robot
2023-07-13 13:25 ` kernel test robot
2023-07-13 13:25 ` [LTP] " kernel test robot
2023-07-13 15:09 ` [Cluster-devel] " Christoph Hellwig
2023-07-13 15:09 ` Christoph Hellwig
2023-07-13 15:09 ` [LTP] " Christoph Hellwig
2023-07-13 15:34 ` [Cluster-devel] " Cyril Hrubis
2023-07-13 15:34 ` Cyril Hrubis
2023-07-13 15:34 ` Cyril Hrubis
2023-07-13 15:56 ` [Cluster-devel] " Christoph Hellwig
2023-07-13 15:56 ` Christoph Hellwig
2023-07-13 15:56 ` Christoph Hellwig
2023-07-14 11:50 ` [Cluster-devel] " Jan Stancek
2023-07-14 11:50 ` Jan Stancek
2023-07-14 11:50 ` Jan Stancek
2023-07-14 11:53 ` Cyril Hrubis [this message]
2023-07-14 11:53 ` Cyril Hrubis
2023-07-14 11:53 ` Cyril Hrubis
2023-07-13 15:12 ` [Cluster-devel] " Cyril Hrubis
2023-07-13 15:12 ` Cyril Hrubis
2023-07-13 15:12 ` 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=ZLE3Vh5yHq_floF7@yuki \
--to=chrubis@suse.cz \
/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.