From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Jinke Han <hanjinke.666-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Muchun Song <songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3] block: don't allow the same type rq_qos add more than once
Date: Tue, 19 Jul 2022 10:56:04 -0600 [thread overview]
Message-ID: <036e5ae0-4908-d4ab-c2e5-56e9ca85e26d@kernel.dk> (raw)
In-Reply-To: <20220719165313.51887-1-hanjinke.666-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
On 7/19/22 10:53 AM, Jinke Han wrote:
> From: Jinke Han <hanjinke.666-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
>
> In our test of iocost, we encounttered some list add/del corrutions of
> inner_walk list in ioc_timer_fn.
This still fails for 5.20 and you didn't correct any of the spelling
mistakes I identified.
Please take your time to get this right rather than attempt to rush it
and needing to send new versions all of the time.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Jinke Han <hanjinke.666@bytedance.com>, tj@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, Muchun Song <songmuchun@bytedance.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] block: don't allow the same type rq_qos add more than once
Date: Tue, 19 Jul 2022 10:56:04 -0600 [thread overview]
Message-ID: <036e5ae0-4908-d4ab-c2e5-56e9ca85e26d@kernel.dk> (raw)
In-Reply-To: <20220719165313.51887-1-hanjinke.666@bytedance.com>
On 7/19/22 10:53 AM, Jinke Han wrote:
> From: Jinke Han <hanjinke.666@bytedance.com>
>
> In our test of iocost, we encounttered some list add/del corrutions of
> inner_walk list in ioc_timer_fn.
This still fails for 5.20 and you didn't correct any of the spelling
mistakes I identified.
Please take your time to get this right rather than attempt to rush it
and needing to send new versions all of the time.
--
Jens Axboe
next prev parent reply other threads:[~2022-07-19 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 16:53 [PATCH v3] block: don't allow the same type rq_qos add more than once Jinke Han
[not found] ` <20220719165313.51887-1-hanjinke.666-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
2022-07-19 16:56 ` Jens Axboe [this message]
2022-07-19 16:56 ` Jens Axboe
[not found] ` <036e5ae0-4908-d4ab-c2e5-56e9ca85e26d-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2022-07-19 17:12 ` [External] " hanjinke
2022-07-19 17:12 ` hanjinke
2022-07-20 9:36 ` [PATCH v4] " Jinke Han
2022-07-20 9:36 ` Jinke Han
[not found] ` <20220720093616.70584-1-hanjinke.666-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
2022-07-20 12:46 ` Jens Axboe
2022-07-20 12:46 ` Jens Axboe
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=036e5ae0-4908-d4ab-c2e5-56e9ca85e26d@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hanjinke.666-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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.