From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@kernel.org>, Sasha Levin <sashal@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ltp@lists.linux.it, Li Wang <liwang@redhat.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Cyril Hrubis <chrubis@suse.cz>,
xishi.qiuxishi@alibaba-inc.com
Subject: Re: [PATCH] hugetlbfs: fix hugetlb page migration/fault race causing SIGBUS
Date: Mon, 12 Aug 2019 15:14:12 +0200 [thread overview]
Message-ID: <39b59001-55c1-a98b-75df-3a5dcec74504@suse.cz> (raw)
In-Reply-To: <20190812084524.GC5117@dhcp22.suse.cz>
On 8/12/19 10:45 AM, Michal Hocko wrote:
> On Sun 11-08-19 19:46:14, Sasha Levin wrote:
>> On Fri, Aug 09, 2019 at 03:17:18PM -0700, Andrew Morton wrote:
>>> On Fri, 9 Aug 2019 08:46:33 +0200 Michal Hocko <mhocko@kernel.org> wrote:
>>>
>>> It should work if we ask stable trees maintainers not to backport
>>> such patches.
>>>
>>> Sasha, please don't backport patches which are marked Fixes-no-stable:
>>> and which lack a cc:stable tag.
>>
>> I'll add it to my filter, thank you!
>
> I would really prefer to stick with Fixes: tag and stable only picking
> up cc: stable patches. I really hate to see workarounds for sensible
> workflows (marking the Fixes) just because we are trying to hide
> something from stable maintainers. Seriously, if stable maintainers have
> a different idea about what should be backported, it is their call. They
> are the ones to deal with regressions and the backporting effort in
> those cases of disagreement.
+1 on not replacing Fixes: tag with some other name, as there might be
automation (not just at SUSE) relying on it.
As a compromise, we can use something else to convey the "maintainers
really don't recommend a stable backport", that Sasha can add to his filter.
Perhaps counter-intuitively, but it could even look like this:
Cc: stable@vger.kernel.org # not recommended at all by maintainer
next prev parent reply other threads:[~2019-08-12 13:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 0:05 [PATCH] hugetlbfs: fix hugetlb page migration/fault race causing SIGBUS Mike Kravetz
2019-08-08 3:36 ` Naoya Horiguchi
2019-08-08 7:46 ` Michal Hocko
2019-08-08 7:47 ` Michal Hocko
2019-08-08 16:55 ` Mike Kravetz
2019-08-08 18:53 ` Michal Hocko
2019-08-08 23:39 ` Andrew Morton
2019-08-09 6:46 ` Michal Hocko
2019-08-09 22:17 ` Andrew Morton
2019-08-11 23:46 ` Sasha Levin
2019-08-12 8:45 ` Michal Hocko
2019-08-12 13:14 ` Vlastimil Babka [this message]
2019-08-12 13:22 ` Michal Hocko
2019-08-12 15:33 ` Sasha Levin
2019-08-12 16:09 ` Qian Cai
2019-08-12 21:37 ` Andrew Morton
2019-08-13 8:43 ` Michal Hocko
2019-08-08 2:24 裘稀石(稀石)
2019-08-08 2:44 ` Mike Kravetz
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=39b59001-55c1-a98b-75df-3a5dcec74504@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=chrubis@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=sashal@kernel.org \
--cc=xishi.qiuxishi@alibaba-inc.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;
as well as URLs for NNTP newsgroup(s).