From: Greg KH <gregkh@linuxfoundation.org>
To: Jack Qiu <jack.qiu@huawei.com>
Cc: stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: init dirty_secmap incorrectly
Date: Mon, 30 Nov 2020 09:11:59 +0100 [thread overview]
Message-ID: <X8SpT6J7VSDibHal@kroah.com> (raw)
In-Reply-To: <20201130073719.8982-1-jack.qiu@huawei.com>
On Mon, Nov 30, 2020 at 03:37:19PM +0800, Jack Qiu wrote:
> section is dirty, but dirty_secmap may not set
>
> Reported-by: Jia Yang <jiayang5@huawei.com>
> Fixes: da52f8ade40b ("f2fs: get the right gc victim section when section
> has several segments")
>
> Signed-off-by: Jack Qiu <jack.qiu@huawei.com>
> ---
> v2:
> - cc stable mailing list
> fs/f2fs/segment.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jack Qiu <jack.qiu@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, stable@vger.kernel.org
Subject: Re: [PATCH] f2fs: init dirty_secmap incorrectly
Date: Mon, 30 Nov 2020 09:11:59 +0100 [thread overview]
Message-ID: <X8SpT6J7VSDibHal@kroah.com> (raw)
In-Reply-To: <20201130073719.8982-1-jack.qiu@huawei.com>
On Mon, Nov 30, 2020 at 03:37:19PM +0800, Jack Qiu wrote:
> section is dirty, but dirty_secmap may not set
>
> Reported-by: Jia Yang <jiayang5@huawei.com>
> Fixes: da52f8ade40b ("f2fs: get the right gc victim section when section
> has several segments")
>
> Signed-off-by: Jack Qiu <jack.qiu@huawei.com>
> ---
> v2:
> - cc stable mailing list
> fs/f2fs/segment.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2020-11-30 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 7:37 [f2fs-dev] [PATCH] f2fs: init dirty_secmap incorrectly Jack Qiu
2020-11-30 7:37 ` Jack Qiu
2020-11-30 8:11 ` Greg KH [this message]
2020-11-30 8:11 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-12-01 7:45 [f2fs-dev] " Jack Qiu
2020-12-02 1:52 ` Chao Yu
2020-12-02 1:52 ` Chao Yu
2020-11-28 6:54 Jack Qiu
2020-11-28 8:49 ` 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=X8SpT6J7VSDibHal@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jack.qiu@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=stable@vger.kernel.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.