linux-kernel - Re: [PATCH 5.4 051/389] epoll: autoremove wakers even more aggressively

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]

Date:   Thu, 27 Oct 2022 12:09:30 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Shakeel Butt <shakeelb@...gle.com>
Cc:     Michele Jr De Candia <mdecandia@...il.com>,
        akpm@...ux-foundation.org, bsegall@...gle.com, edumazet@...gle.com,
        jbaron@...mai.com, khazhy@...gle.com, linux-kernel@...r.kernel.org,
        r@....cc, rpenyaev@...e.de, stable@...nel.org,
        stable@...r.kernel.org, torvalds@...ux-foundation.org,
        viro@...iv.linux.org.uk
Subject: Re: [PATCH 5.4 051/389] epoll: autoremove wakers even more
 aggressively

On Wed, Oct 26, 2022 at 11:48:01AM -0700, Shakeel Butt wrote:
> On Wed, Oct 26, 2022 at 11:44 AM Michele Jr De Candia
> <mdecandia@...il.com> wrote:
> >
> > Hi Greg,
> > sorry for the confusion.
> >
> > I'm running a container-based app on top of Ubuntu Linux 20.04 and linux kernel 5.4 always updated with latest patches.
> >
> > Updating from 5.4.210 to 5.4.211 we faced the hang up issue and searching for the cause we have tested that
> > hangup occurs only with this patch
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y&id=cf2db24ec4b8e9d399005ececd6f6336916ab6fc
> >
> > While understanding root cause, wt the moment we reverted it and hang up does not occurs (actually we are running 5.4.219 without that patch).
> >
> > Michele
> >
> 
> Hi Michele, can you try the latest upstream kernel and see if the
> issue repro ther? Also is it possible to provide a simplified repro of
> the issue?

Also is this issue on 5.10.y and 5.15.y?

thanks,

greg k-h