OCFS2-Devel Archive mirror
 help / color / mirror / Atom feed
From: Joseph Qi via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ocfs2-devel <ocfs2-devel@oss.oracle.com>
Subject: Re: [Ocfs2-devel] [PATCH v2] ocfs2: fix non-auto defrag path not working issue
Date: Fri, 24 Feb 2023 10:09:35 +0800	[thread overview]
Message-ID: <455fe625-9039-cc8b-f846-b3df85d9488c@linux.alibaba.com> (raw)
In-Reply-To: <20230223130715.8df852c1630b9103097489ec@linux-foundation.org>



On 2/24/23 5:07 AM, Andrew Morton wrote:
> On Mon, 20 Feb 2023 14:26:19 +0800 Joseph Qi <joseph.qi@linux.alibaba.com> wrote:
> 
>>> Currently there is no tools triggering the above issues since
>>> defragfs.ocfs2 enables auto defrag by default. Test with manually
>>> changing defragfs.ocfs2 to run non auto defrag path.
>>>
>>> Signed-off-by: Heming Zhao <heming.zhao@suse.com>
>>
>> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> 
> Thanks.  I added a cc:stable tag to both these patches so the
> fixes get backported into earlier kernels.

Thanks for your meticulousness.

Joseph

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

      reply	other threads:[~2023-02-24  2:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  5:05 [Ocfs2-devel] [PATCH v2] ocfs2: fix non-auto defrag path not working issue Heming Zhao via Ocfs2-devel
2023-02-20  6:26 ` Joseph Qi via Ocfs2-devel
2023-02-23 21:07   ` Andrew Morton via Ocfs2-devel
2023-02-24  2:09     ` Joseph Qi via Ocfs2-devel [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=455fe625-9039-cc8b-f846-b3df85d9488c@linux.alibaba.com \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=joseph.qi@linux.alibaba.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).