linux-kernel - Re: Upstream fixes not merged in 5.4.y

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20200720121543.GA2984743@kroah.com>
Date:   Mon, 20 Jul 2020 14:15:43 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     SeongJae Park <sjpark@...zon.com>
Cc:     sashal@...nel.org, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: Upstream fixes not merged in 5.4.y

On Mon, Jun 29, 2020 at 04:28:05PM +0200, SeongJae Park wrote:
> Hello,
> 
> 
> With my little script, I found below commits in the mainline tree are more than
> 1 week old and fixing commits that back-ported in v5.4..v5.4.49, but not merged
> in the stable/linux-5.4.y tree.  Are those need to be merged in but missed or
> dealyed?
> 
> 9210c075cef2 ("nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll()")

I tried this first patch, and it doesn't apply to the 5.4.y tree, so are
you sure you tried these yourself?

If so, please send a series of backported patches that you have
successfully tested, or if a patch applies cleanly, just the git id.

thanks,

greg k-h