From: Greg KH <greg@kroah.com>
To: zhangshida <starzhangzsd@gmail.com>
Cc: stable@vger.kernel.org, Shida Zhang <zhangshida@kylinos.cn>,
stable@kernel.org, Andreas Dilger <adilger@dilger.ca>,
"Darrick J . Wong" <djwong@kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 4.14.y] ext4: fix rec_len verify error
Date: Sat, 7 Oct 2023 12:19:55 +0200 [thread overview]
Message-ID: <2023100748-hesitancy-conical-8060@gregkh> (raw)
In-Reply-To: <20230924021955.2256033-1-zhangshida@kylinos.cn>
On Sun, Sep 24, 2023 at 10:19:55AM +0800, zhangshida wrote:
> From: Shida Zhang <zhangshida@kylinos.cn>
>
> [ Upstream commit 7fda67e8c3ab6069f75888f67958a6d30454a9f6 ]
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-10-07 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:58 FAILED: patch "[PATCH] ext4: fix rec_len verify error" failed to apply to 4.14-stable tree gregkh
2023-09-22 5:39 ` [PATCH] ext4: fix rec_len verify error zhangshida
2023-09-22 9:23 ` Greg KH
2023-09-22 15:11 ` Theodore Ts'o
2023-09-24 2:19 ` [PATCH 4.14.y] " zhangshida
2023-10-07 10:19 ` Greg KH [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=2023100748-hesitancy-conical-8060@gregkh \
--to=greg@kroah.com \
--cc=adilger@dilger.ca \
--cc=djwong@kernel.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=starzhangzsd@gmail.com \
--cc=tytso@mit.edu \
--cc=zhangshida@kylinos.cn \
/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