From: Eric Biggers <ebiggers@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 5.15 00/10] ext4 fast-commit fixes for 5.15-stable
Date: Tue, 17 Jan 2023 22:29:36 +0000 [thread overview]
Message-ID: <Y8chUKeNaULEhM+V@gmail.com> (raw)
In-Reply-To: <Y7a8B2+AjwxpmTfh@kroah.com>
Hi Greg,
On Thu, Jan 05, 2023 at 01:01:11PM +0100, Greg KH wrote:
> On Wed, Jan 04, 2023 at 11:13:49PM -0800, Eric Biggers wrote:
> > This series backports 6 commits with 'Cc stable' that had failed to be
> > applied, and 4 related commits that made the backports much easier.
> > Please apply this series to 5.15-stable.
> >
> > I verified that this series does not cause any regressions with
> > 'gce-xfstests -c ext4/fast_commit -g auto'. There is one test failure
> > both before and after (ext4/050).
>
> All now queued up, thanks.
>
> greg k-h
It's too late to fix now, but the commits in 5.15-stable all use
"Eric Biggers <ebiggers@kernel.org>" as the author instead of the From line in
the patch itself. For example, patch 1 became:
commit b0ed9a032e52a175683d18e2e2e8eec0f9ba1ff9
Author: Eric Biggers <ebiggers@kernel.org>
Date: Wed Jan 4 23:13:50 2023 -0800
ext4: remove unused enum EXT4_FC_COMMIT_FAILED
From: Ritesh Harjani <riteshh@linux.ibm.com>
commit c864ccd182d6ff2730a0f5b636c6b7c48f6f4f7f upstream.
For reference, the upstream commit is:
commit c864ccd182d6ff2730a0f5b636c6b7c48f6f4f7f
Author: Ritesh Harjani <riteshh@linux.ibm.com>
Date: Sat Mar 12 11:09:46 2022 +0530
ext4: remove unused enum EXT4_FC_COMMIT_FAILED
Do you know how this happened, and how it can be prevented in the future? I
think I sent everything out correctly, so I think this is something on your end.
- Eric
next prev parent reply other threads:[~2023-01-17 22:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 7:13 [PATCH 5.15 00/10] ext4 fast-commit fixes for 5.15-stable Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 01/10] ext4: remove unused enum EXT4_FC_COMMIT_FAILED Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 02/10] ext4: use ext4_debug() instead of jbd_debug() Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 03/10] ext4: introduce EXT4_FC_TAG_BASE_LEN helper Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 04/10] ext4: factor out ext4_fc_get_tl() Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 05/10] ext4: fix potential out of bound read in ext4_fc_replay_scan() Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 06/10] ext4: disable fast-commit of encrypted dir operations Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 07/10] ext4: don't set up encryption key during jbd2 transaction Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 08/10] ext4: add missing validation of fast-commit record lengths Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 09/10] ext4: fix unaligned memory access in ext4_fc_reserve_space() Eric Biggers
2023-01-05 7:13 ` [PATCH 5.15 10/10] ext4: fix off-by-one errors in fast-commit block filling Eric Biggers
2023-01-05 12:01 ` [PATCH 5.15 00/10] ext4 fast-commit fixes for 5.15-stable Greg KH
2023-01-17 22:29 ` Eric Biggers [this message]
2023-01-18 6:15 ` Greg KH
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=Y8chUKeNaULEhM+V@gmail.com \
--to=ebiggers@kernel.org \
--cc=greg@kroah.com \
--cc=linux-ext4@vger.kernel.org \
--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 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).