From: Xiubo Li <xiubli@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: ceph: don't truncate file in atomic_open
Date: Thu, 13 Oct 2022 17:20:25 +0800 [thread overview]
Message-ID: <0130f352-cf2a-ab9a-3da9-8aae1bd464ca@redhat.com> (raw)
In-Reply-To: <Y0fWbKksISUWcCeA@kroah.com>
Hi Greg,
On 13/10/2022 17:12, Greg KH wrote:
> On Wed, Oct 12, 2022 at 09:51:43AM +0800, Xiubo Li wrote:
>> Hi Maitainers
>>
>> This patch is a fix in kceph module and should be backported to any affected
>> stable old kernels. And the original patch missed tagging stable and got
>> merged already months ago:
> Does not apply to the trees, sorry. Please provide a working backport
> if you wish to see it applied.
Already sent it out and I saw your have applied to them.
Thanks very much!
- Xiubo
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2022-10-13 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59d7c10f-7419-971b-c13c-71865f897953@redhat.com>
[not found] ` <20220701025227.21636-1-sehuww@mail.scut.edu.cn>
2022-10-12 1:51 ` ceph: don't truncate file in atomic_open Xiubo Li
2022-10-13 3:30 ` Xiubo Li
2022-10-13 9:15 ` Greg KH
2022-10-13 9:12 ` Greg KH
2022-10-13 9:20 ` Xiubo Li [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=0130f352-cf2a-ab9a-3da9-8aae1bd464ca@redhat.com \
--to=xiubli@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox