From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
stable@vger.kernel.org, cel@kernel.org
Subject: Re: [PATCH 6.1 1/5] NFSD: initialize copy->cp_clp early in nfsd4_copy for use by trace point
Date: Tue, 19 Nov 2024 10:30:10 -0500 [thread overview]
Message-ID: <ZzyvAnV1p00w5f2_@sashalap> (raw)
In-Reply-To: <2024111915-annually-semisoft-c5d6@gregkh>
On Tue, Nov 19, 2024 at 03:13:51PM +0100, Greg KH wrote:
>On Tue, Nov 19, 2024 at 09:06:30AM -0500, Chuck Lever wrote:
>> On Mon, Nov 18, 2024 at 11:36:15PM -0500, Sasha Levin wrote:
>> > [ Sasha's backport helper bot ]
>> >
>> > Hi,
>> >
>> > The upstream commit SHA1 provided is correct: 15d1975b7279693d6f09398e0e2e31aca2310275
>> >
>> > WARNING: Author mismatch between patch and upstream commit:
>> > Backport author: cel@kernel.org
>> > Commit author: Dai Ngo <dai.ngo@oracle.com>
>>
>> Is this a bug in my backport script? Should patches backported
>> to LTS retain the upstream patch author, or should they be From:
>> the backporter? If the former, I can adjust my scripts.
>
>No, this is correct, I think Sasha's scripts are a bit too sensitive
>here and in a few other places.
Right, sorry - this is more of an indicator for me to say "this patch
was backported by someone who's not the author, review it more
carefully".
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-19 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 21:18 [PATCH 6.1 0/5] Address CVE-2024-49974 cel
2024-11-18 21:18 ` [PATCH 6.1 1/5] NFSD: initialize copy->cp_clp early in nfsd4_copy for use by trace point cel
2024-11-19 4:36 ` Sasha Levin
2024-11-19 14:06 ` Chuck Lever
2024-11-19 14:13 ` Greg KH
2024-11-19 15:30 ` Sasha Levin [this message]
2024-11-19 15:31 ` Chuck Lever III
2024-11-18 21:18 ` [PATCH 6.1 2/5] NFSD: Async COPY result needs to return a write verifier cel
2024-11-19 4:36 ` Sasha Levin
2024-11-18 21:18 ` [PATCH 6.1 3/5] NFSD: Limit the number of concurrent async COPY operations cel
2024-11-19 4:36 ` Sasha Levin
2024-11-18 21:18 ` [PATCH 6.1 4/5] NFSD: Initialize struct nfsd4_copy earlier cel
2024-11-19 4:36 ` Sasha Levin
2024-11-18 21:19 ` [PATCH 6.1 5/5] NFSD: Never decrement pending_async_copies on error cel
2024-11-19 4:36 ` Sasha Levin
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=ZzyvAnV1p00w5f2_@sashalap \
--to=sashal@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=gregkh@linuxfoundation.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 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.