[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <6021D755-F883-4524-B3D1-07C03C7DF11B@redhat.com>
Date: Tue, 10 Mar 2020 23:02:58 +0100
From: David Hildenbrand <david@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: David Hildenbrand <david@...hat.com>,
David Rientjes <rientjes@...gle.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
virtualization@...ts.linux-foundation.org,
Jason Wang <jasowang@...hat.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Tyler Sanderson <tysand@...gle.com>,
Wei Wang <wei.w.wang@...el.com>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
Nadav Amit <namit@...are.com>,
Michal Hocko <mhocko@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v3] virtio-balloon: Switch back to OOM handler for VIRTIO_BALLOON_F_DEFLATE_ON_OOM
> Am 10.03.2020 um 22:25 schrieb Michael S. Tsirkin <mst@...hat.com>:
>
> On Tue, Mar 10, 2020 at 08:13:19PM +0100, David Hildenbrand wrote:
>>> Should this have:
>>>
>>> Cc: stable@...r.kernel.org # 4.19+
>>
>> I guess as nothing will actually "crash" it's not worth stable.
>
>
> No - it's a regression, it would be a stable candidate from that POV.
AFAIK
„ It must fix a problem that causes a build error (but not for things marked CONFIG_BROKEN), an oops, a hang, data corruption, a real security issue, or some “oh, that’s not good” issue. In short, something critical.“
If this regression is that critical is debatable. But it doesn‘t matter as you correctly say, it‘s too big :)
Powered by blists - more mailing lists