From: Bart Van Assche <bvanassche@acm.org>
To: eunhee83.rho@samsung.com, Yi Zhang <yi.zhang@redhat.com>,
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: Fri, 1 Mar 2024 08:33:54 -0800 [thread overview]
Message-ID: <399ee6af-c1da-40ab-a679-065aa82f41ab@acm.org> (raw)
In-Reply-To: <CAHj4cs_eOSafp0=cbwjNPR6X2342GF_cnUTcXf6RjrMnoOHSmQ@mail.gmail.com>
On 2/29/24 23:49, Yi Zhang wrote:
> Bisect shows it was introduced with the below commit:
>
> commit dbf8e63f48af48f3f0a069fc971c9826312dbfc1
> Author: Eunhee Rho <eunhee83.rho@samsung.com>
> Date: Mon Aug 1 13:40:02 2022 +0900
>
> f2fs: remove device type check for direct IO
(+Eunhee)
Thank you Yi for having bisected this issue. I know this takes
considerable effort.
Eunhee, please take a look at this bug report:
https://lore.kernel.org/all/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/
Thanks,
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: eunhee83.rho@samsung.com, Yi Zhang <yi.zhang@redhat.com>,
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: Fri, 1 Mar 2024 08:33:54 -0800 [thread overview]
Message-ID: <399ee6af-c1da-40ab-a679-065aa82f41ab@acm.org> (raw)
In-Reply-To: <CAHj4cs_eOSafp0=cbwjNPR6X2342GF_cnUTcXf6RjrMnoOHSmQ@mail.gmail.com>
On 2/29/24 23:49, Yi Zhang wrote:
> Bisect shows it was introduced with the below commit:
>
> commit dbf8e63f48af48f3f0a069fc971c9826312dbfc1
> Author: Eunhee Rho <eunhee83.rho@samsung.com>
> Date: Mon Aug 1 13:40:02 2022 +0900
>
> f2fs: remove device type check for direct IO
(+Eunhee)
Thank you Yi for having bisected this issue. I know this takes
considerable effort.
Eunhee, please take a look at this bug report:
https://lore.kernel.org/all/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/
Thanks,
Bart.
_______________________________________________
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-03-01 16:33 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
2024-02-28 12:08 ` [f2fs-dev] " Yi Zhang
2024-03-01 7:49 ` Yi Zhang
2024-03-01 16:33 ` Bart Van Assche [this message]
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=399ee6af-c1da-40ab-a679-065aa82f41ab@acm.org \
--to=bvanassche@acm.org \
--cc=chao@kernel.org \
--cc=eunhee83.rho@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yi.zhang@redhat.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.