From: Su Yue <glass.su@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ocfs2-devel@lists.linux.dev, Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH v2 0/4] ocfs2 bugs fixes exposed by fstests
Date: Thu, 4 Apr 2024 13:54:39 +0800 [thread overview]
Message-ID: <4CA64332-E3A7-4DA3-93C1-60227FE18EEA@suse.com> (raw)
In-Reply-To: <20240403185138.3aaf5aace1b407eff7ed530d@linux-foundation.org>
> On Apr 4, 2024, at 09:51, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 2 Apr 2024 09:46:47 +0800 Su Yue <glass.su@suse.com> wrote:
>
>> The patchset is to fix some wrong behavior of ocfs2 exposed
>> by fstests.
>
> Thanks. We should consider which of these fixes should be backported
> into -stable kernels. For that we should provide, for each patch:
>
> - A description of the userspace-visible impact of the bug and
>
Yeah. I should elaborate more in cover letter.
> - A suitable Fixes: target to tell -stable maintainers how far back
> these fixes are needed.
>
Necessary Indeed.
> Please could we give some consideration to these matters?
>
Sure. I will do these after vacation in next version.
prev parent reply other threads:[~2024-04-04 5:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 1:46 [PATCH v2 0/4] ocfs2 bugs fixes exposed by fstests Su Yue
2024-04-02 1:46 ` [PATCH v2 1/4] ocfs2: return real error code in ocfs2_dio_wr_get_block Su Yue
2024-04-02 1:51 ` Joseph Qi
2024-04-02 1:46 ` [PATCH v2 2/4] ocfs2: fix races between hole punching and AIO+DIO Su Yue
2024-04-02 1:46 ` [PATCH v2 3/4] ocfs2: update inode fsync transaction id in ocfs2_unlink and ocfs2_link Su Yue
2024-04-02 1:46 ` [PATCH v2 4/4] ocfs2: use coarse time for new created files Su Yue
2024-04-04 1:51 ` [PATCH v2 0/4] ocfs2 bugs fixes exposed by fstests Andrew Morton
2024-04-04 5:54 ` Su Yue [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=4CA64332-E3A7-4DA3-93C1-60227FE18EEA@suse.com \
--to=glass.su@suse.com \
--cc=akpm@linux-foundation.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=ocfs2-devel@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).