From: Joseph Salisbury <joseph.salisbury@oracle.com>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Joseph Salisbury <jsalisbury@kernel.org>,
Dan Shelton <dan.f.shelton@gmail.com>,
Martin Wege <martin.l.wege@gmail.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
chuck.lever@oracle.com
Subject: Re: [External] : Re: Linux 5.15-rt still misses commit "NFSD: Fix NFSv4's PUTPUBFH operation"
Date: Tue, 5 Nov 2024 15:41:53 -0500 [thread overview]
Message-ID: <595e91af-7737-4567-94e6-6f97a281354f@oracle.com> (raw)
In-Reply-To: <d370e7e6-9b33-4901-b49b-699e1932dc49@oracle.com>
On 11/4/24 12:10, Joseph Salisbury wrote:
>
>
>
> On 11/4/24 09:06, Cedric Blancher wrote:
>> On Mon, 4 Nov 2024 at 14:53, Joseph Salisbury
>> <joseph.salisbury@oracle.com> wrote:
>>>
>>>
>>>
>>> On 11/4/24 08:24, Sebastian Andrzej Siewior wrote:
>>>> On 2024-11-04 13:01:42 [+0100], Cedric Blancher wrote:
>>>>> Good lunchtime!
>>>> Hi,
>>>>
>>>>> Linux 5.15-rt in linux-stable-rt.git still misses commit "NFSD: Fix
>>>>> NFSv4's PUTPUBFH operation":
>>>>> Title: "NFSD: Fix NFSv4's PUTPUBFH operation"
>>>>> commit 202f39039a11402dcbcd5fece8d9fa6be83f49ae upstream.
>>>>>
>>>>> Could you please add this missing commit to the 5.15-RT branch in
>>>>> linux-stable-rt.git? Thank you!
>>>>>
>>>>> References:
>>>>> https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.170&id=2f8f226f4d56fae0fabec23cf0af82c43cb4dce0__;!!ACWV5N9M2RV99hQ!J_i5oEOgM6dLLOAkgjiM9ncalWBDCr_5-CaHZBZI8r2RU3TtvlTNnrOBlTBiS6Z0M3ETfv4emw1N632COpow2bNbsDE$
>>>>>
>>>> The v5.15-RT series is based on v5.15.167. The 170 minor release is
>>>> from
>>>> 2024-11-01. The commit will be picked as part of the update to 170.
>>>>
>>>> There is v5.15.167-rt80-rc1 is preparation, I guess 170 will be next.
>>> What Sebastian says is correct. v5.15.167-rc80-rc1 is out for testing.
>>> This version has a release candidate, since it introduces a new patch:
>>> 4a1d3acd6ea8 ("netfilter: nft_counter: Use u64_stats_t for
>>> statistic.").
>>>
>>> Version v5.15.167-rc80 should be released the end of this week.
>>> Currently v5.15.170 is the latest stable release. I should be
>>> releasing
>>> v5.15.170-rc81 next week (Or whichever is the latest stable release is,
>>> if a newer than 170 one comes out prior to my release).
>>>
>> Could you please just manually pull this patch in?
> We generally don't create releases for individual patches that come in
> via stable releases.
>
> If you need this patch due to a time constraint, I can release
> v5.15.170-rc81, which includes this patch, immediately following
> v5.15.167-rt80. That would be towards the end of the week to ensure
> proper testing and allowing for feedback of v5.15.167-rt80-rc1.
>
>>
>> Ced
>
Hi Cedric,
The v5.15.170-rt81 patchset is now available. This release has the
commit you were interested in:
2f8f226f4d56f ("NFSD: Fix NFSv4's PUTPUBFH operation")
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v5.15-rt
Head SHA1: 67017c496f78e15598f48bb3115e3641a82ae507
Or to build 5.15.170-rt81 directly, the following patches should be applied:
https://www.kernel.org/pub/linux/kernel/projects/rt/5.15
https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.15.tar.xz
https://www.kernel.org/pub/linux/kernel/v5.x/patch-5.15.170.xz
https://www.kernel.org/pub/linux/kernel/projects/rt/5.15/patch-5.15.170-rt81.patch.xz
Thanks,
Joe
next prev parent reply other threads:[~2024-11-05 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALXu0Udop9Qx_N8KwScmGk+j3NrfDry1r-Fk=5bc+9EXsfnB=w@mail.gmail.com>
[not found] ` <20241104132412.dFx8w7ZH@linutronix.de>
2024-11-04 13:53 ` Joseph Salisbury
2024-11-04 14:06 ` Cedric Blancher
2024-11-04 17:10 ` Joseph Salisbury
2024-11-05 20:41 ` Joseph Salisbury [this message]
2024-11-20 7:39 ` Cedric Blancher
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=595e91af-7737-4567-94e6-6f97a281354f@oracle.com \
--to=joseph.salisbury@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=cedric.blancher@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=dan.f.shelton@gmail.com \
--cc=jsalisbury@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=martin.l.wege@gmail.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
all inboxes | Powered by JetHome®