linux-kernel - Re: [PATCH 5.8 050/124] drm/vmwgfx: Fix error handling in get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201014065522.GA2762376@kroah.com>
Date:   Wed, 14 Oct 2020 08:55:22 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Roland Scheidegger <sroland@...are.com>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Zack Rusin <zackr@...are.com>,
        Martin Krastev <krastevm@...are.com>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.8 050/124] drm/vmwgfx: Fix error handling in get_node

On Tue, Oct 13, 2020 at 05:55:31PM +0200, Roland Scheidegger wrote:
> Hi,
> 
> this commit should NOT be applied to 5.8.
> It fixes a regression introduced by
> 58e4d686d456c3e356439ae160ff4a0728940b8e (drm/ttm: cleanup
> ttm_mem_type_manager_func.get_node interface v3) which is part of 5.9
> but not 5.8.
> Applying this to 5.8 will very likely break things. I don't know why it
> ended up as a candidate for 5.8.

Now dropped, thanks.  And it was probably picked up due to the wording
in the changelog text, along with a lack of a "Fixes:" tag that pointed
at the exact change it fixed up, which would have shown that this is a
5.9-only thing.

thanks,

greg k-h