From: Yi Zhang <yi.zhang@redhat.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
linux-block <linux-block@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>
Subject: Re: [bug report]WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 iomap_iter+0x32b observed with blktests zbd/010
Date: Wed, 28 Feb 2024 20:08:49 +0800 [thread overview]
Message-ID: <CAHj4cs874FivTdmw=VMJwTzzLFZWb4OKqvNGRN0R0O+Oiv4aYA@mail.gmail.com> (raw)
In-Reply-To: <esesb6dg5omj7e5sdnltnapuuzgmbdfmezcz6owsx2waqayc5q@36yhz4dmrxh6>
On Wed, Feb 28, 2024 at 7:09 PM Shinichiro Kawasaki
<shinichiro.kawasaki@wdc.com> wrote:
>
> On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> > Hello
> > I reproduced this issue on the latest linux-block/for-next, please
> > help check it and let me know if you need more info/test, thanks.
>
> [...]
>
> > [ 4381.278858] ------------[ cut here ]------------
> > [ 4381.283484] WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51
> > iomap_iter+0x32b/0x350
>
> I can not recreate the WARN and the failure on my test machines. On the other
> hand, it is repeatedly recreated on CKI test machines since Feb/19/2024 [1].
>
> [1] https://datawarehouse.cki-project.org/issue/2508
>
> I assume that a kernel change triggered the failure.
>
> Yi, is it possible to bisect and identify the trigger commit using CKI test
> machines? The failure is observed with v6.6.17 and v6.6.18 kernel. I guess the
> failure was not observed with v6.6.16 kernel, so I suggest to bisect between
Sure, will try to bisect it later this week. :)
> v6.6.16 and v6.6.17.
>
--
Best Regards,
Yi Zhang
WARNING: multiple messages have this Message-ID (diff)
From: Yi Zhang <yi.zhang@redhat.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block <linux-block@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [bug report]WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 iomap_iter+0x32b observed with blktests zbd/010
Date: Wed, 28 Feb 2024 20:08:49 +0800 [thread overview]
Message-ID: <CAHj4cs874FivTdmw=VMJwTzzLFZWb4OKqvNGRN0R0O+Oiv4aYA@mail.gmail.com> (raw)
In-Reply-To: <esesb6dg5omj7e5sdnltnapuuzgmbdfmezcz6owsx2waqayc5q@36yhz4dmrxh6>
On Wed, Feb 28, 2024 at 7:09 PM Shinichiro Kawasaki
<shinichiro.kawasaki@wdc.com> wrote:
>
> On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> > Hello
> > I reproduced this issue on the latest linux-block/for-next, please
> > help check it and let me know if you need more info/test, thanks.
>
> [...]
>
> > [ 4381.278858] ------------[ cut here ]------------
> > [ 4381.283484] WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51
> > iomap_iter+0x32b/0x350
>
> I can not recreate the WARN and the failure on my test machines. On the other
> hand, it is repeatedly recreated on CKI test machines since Feb/19/2024 [1].
>
> [1] https://datawarehouse.cki-project.org/issue/2508
>
> I assume that a kernel change triggered the failure.
>
> Yi, is it possible to bisect and identify the trigger commit using CKI test
> machines? The failure is observed with v6.6.17 and v6.6.18 kernel. I guess the
> failure was not observed with v6.6.16 kernel, so I suggest to bisect between
Sure, will try to bisect it later this week. :)
> v6.6.16 and v6.6.17.
>
--
Best Regards,
Yi Zhang
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-02-28 12:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 16:58 [bug report]WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 iomap_iter+0x32b observed with blktests zbd/010 Yi Zhang
2024-02-18 16:58 ` [f2fs-dev] " Yi Zhang
2024-02-28 11:08 ` Shinichiro Kawasaki
2024-02-28 11:08 ` [f2fs-dev] " Shinichiro Kawasaki via Linux-f2fs-devel
2024-02-28 12:08 ` Yi Zhang [this message]
2024-02-28 12:08 ` Yi Zhang
2024-03-01 7:49 ` Yi Zhang
2024-03-01 16:33 ` Bart Van Assche
2024-03-01 16:33 ` [f2fs-dev] " Bart Van Assche
2024-03-12 2:52 ` Shinichiro Kawasaki
2024-03-12 2:52 ` [f2fs-dev] " Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-12 4:57 ` Yi Zhang
2024-03-12 9:34 ` Shinichiro Kawasaki
2024-03-12 9:34 ` [f2fs-dev] " Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-18 5:47 ` Shinichiro Kawasaki
2024-03-18 5:47 ` Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-18 21:12 ` Daeho Jeong
2024-03-18 21:12 ` Daeho Jeong
2024-03-19 10:56 ` Shinichiro Kawasaki
2024-03-19 10:56 ` Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-19 2:22 ` Chao Yu
2024-03-19 2:22 ` Chao Yu
2024-03-19 11:13 ` Shinichiro Kawasaki
2024-03-19 11:13 ` Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-24 12:13 ` Chao Yu
2024-03-24 12:13 ` Chao Yu
2024-03-25 2:14 ` Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-25 2:14 ` Shinichiro Kawasaki
2024-03-25 3:06 ` Chao Yu
2024-03-25 3:06 ` Chao Yu
2024-03-25 6:56 ` Shinichiro Kawasaki via Linux-f2fs-devel
2024-03-25 6:56 ` Shinichiro Kawasaki
2024-03-26 3:30 ` Chao Yu
2024-03-26 3:30 ` Chao Yu
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='CAHj4cs874FivTdmw=VMJwTzzLFZWb4OKqvNGRN0R0O+Oiv4aYA@mail.gmail.com' \
--to=yi.zhang@redhat.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=shinichiro.kawasaki@wdc.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.