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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190701170602.2fdb35c2@gandalf.local.home>
Date:   Mon, 1 Jul 2019 17:06:02 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Corey Minyard <cminyard@...sta.com>
Cc:     Corey Minyard <minyard@....org>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>, tglx@...utronix.de
Subject: Re: [PATCH RT v2] Fix a lockup in wait_for_completion() and friends

On Mon, 1 Jul 2019 15:43:25 -0500
Corey Minyard <cminyard@...sta.com> wrote:


> I show that patch is already applied at
> 
>     1921ea799b7dc561c97185538100271d88ee47db
>     sched/completion: Fix a lockup in wait_for_completion()
> 
> git describe --contains 1921ea799b7dc561c97185538100271d88ee47db
> v4.19.37-rt20~1
> 
> So I'm not sure what is going on.

Bah, I'm replying to the wrong commit that I'm having issues with.

I searched your name to find the patch that is of trouble, and picked
this one.

I'll go find the problem patch, sorry for the noise on this one.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ