From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peng Tao <tao.peng@linux.alibaba.com>
Cc: alikernel-developer@linux.alibaba.com,
Liu Bo <bo.liu@linux.alibaba.com>,
Ma Jie Yue <majieyue@linux.alibaba.com>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Eryu Guan <eguan@linux.alibaba.com>,
Miklos Szeredi <mszeredi@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH CK 4.19 1/4] fuse: fix page dereference after free
Date: Mon, 1 Mar 2021 09:05:12 +0100 [thread overview]
Message-ID: <YDygOH7MGVOAYk+H@kroah.com> (raw)
In-Reply-To: <1614569779-12114-2-git-send-email-tao.peng@linux.alibaba.com>
On Mon, Mar 01, 2021 at 11:36:16AM +0800, Peng Tao wrote:
> From: Miklos Szeredi <mszeredi@redhat.com>
>
> commit d78092e4937de9ce55edcb4ee4c5e3c707be0190 upstream.
>
> fix #32833505
What does this mean?
And why are you all backporting random stable kernel patches to your
tree and not just taking all of them with a simple merge?
By selectivly cherry-picking patches like this, you are guaranteed to be
doing more work, and have a much more insecure and buggy kernel. The
opposite of what your end goal should be, correct?
good luck!
greg k-h
next prev parent reply other threads:[~2021-03-01 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1614569779-12114-1-git-send-email-tao.peng@linux.alibaba.com>
2021-03-01 3:36 ` [PATCH CK 4.19 1/4] fuse: fix page dereference after free Peng Tao
2021-03-01 8:05 ` Greg Kroah-Hartman [this message]
2021-03-01 8:52 ` Peng Tao
2021-03-01 9:04 ` Greg Kroah-Hartman
2021-03-01 3:36 ` [PATCH CK 4.19 4/4] fuse: Fix parameter for FS_IOC_{GET,SET}FLAGS Peng Tao
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=YDygOH7MGVOAYk+H@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alikernel-developer@linux.alibaba.com \
--cc=bo.liu@linux.alibaba.com \
--cc=eguan@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=majieyue@linux.alibaba.com \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tao.peng@linux.alibaba.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