From: Christoph Hellwig <hch@infradead.org>
To: Changheun Lee <nanich.lee@samsung.com>
Cc: ming.lei@redhat.com, Damien.LeMoal@wdc.com,
Johannes.Thumshirn@wdc.com, asml.silence@gmail.com,
axboe@kernel.dk, bvanassche@acm.org, gregkh@linuxfoundation.org,
hch@infradead.org, jisoo2146.oh@samsung.com,
junho89.kim@samsung.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, mj0123.lee@samsung.com,
osandov@fb.com, patchwork-bot@kernel.org,
seunghwan.hyun@samsung.com, sookwan7.kim@samsung.com,
tj@kernel.org, tom.leiming@gmail.com, woosung2.lee@samsung.com,
yt0928.kim@samsung.com
Subject: Re: [RESEND,v5,1/2] bio: limit bio max size
Date: Tue, 13 Apr 2021 06:32:58 +0100 [thread overview]
Message-ID: <20210413053258.GA1264305@infradead.org> (raw)
In-Reply-To: <20210413043733.28880-1-nanich.lee@samsung.com>
And more importantly please test with a file system that uses the
iomap direct I/O code (btrfs, gfs2, ext4, xfs, zonefs) as we should
never just work aroudn a legacy codebase that should go away in the
block layer.
prev parent reply other threads:[~2021-04-13 5:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210316080104epcas1p11483035c927c2e65600ae90309334b24@epcas1p1.samsung.com>
2021-03-16 7:44 ` [RESEND PATCH v5 1/2] bio: limit bio max size Changheun Lee
2021-03-16 7:44 ` [RESEND PATCH v5 2/2] bio: add limit_bio_size sysfs Changheun Lee
2021-04-06 21:05 ` Bart Van Assche
2021-04-07 1:21 ` Changheun Lee
2021-04-07 5:43 ` Greg KH
2021-04-06 1:31 ` [RESEND PATCH v5 1/2] bio: limit bio max size Changheun Lee
2021-04-06 7:32 ` Greg KH
2021-04-07 0:16 ` Changheun Lee
2021-04-07 5:05 ` Greg KH
2021-04-07 5:06 ` Changheun Lee
2021-04-07 5:36 ` Greg KH
2021-04-07 6:55 ` Changheun Lee
2021-04-07 7:40 ` Greg KH
2021-04-07 9:28 ` [RESEND,v5,1/2] " Changheun Lee
2021-04-07 10:27 ` Damien Le Moal
2021-04-09 14:47 ` Bart Van Assche
2021-04-11 22:13 ` Damien Le Moal
2021-04-12 3:23 ` Ming Lei
2021-04-13 4:37 ` Changheun Lee
2021-04-13 5:32 ` Christoph Hellwig [this message]
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=20210413053258.GA1264305@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=jisoo2146.oh@samsung.com \
--cc=junho89.kim@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mj0123.lee@samsung.com \
--cc=nanich.lee@samsung.com \
--cc=osandov@fb.com \
--cc=patchwork-bot@kernel.org \
--cc=seunghwan.hyun@samsung.com \
--cc=sookwan7.kim@samsung.com \
--cc=tj@kernel.org \
--cc=tom.leiming@gmail.com \
--cc=woosung2.lee@samsung.com \
--cc=yt0928.kim@samsung.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.