Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 27 Oct 2022 12:09:30 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Shakeel Butt <shakeelb@google.com>
Cc:     Michele Jr De Candia <mdecandia@gmail.com>,
        akpm@linux-foundation.org, bsegall@google.com, edumazet@google.com,
        jbaron@akamai.com, khazhy@google.com, linux-kernel@vger.kernel.org,
        r@hev.cc, rpenyaev@suse.de, stable@kernel.org,
        stable@vger.kernel.org, torvalds@linux-foundation.org,
        viro@zeniv.linux.org.uk
Subject: Re: [PATCH 5.4 051/389] epoll: autoremove wakers even more
 aggressively
Message-ID: <Y1pY2n6E1Xa58MXv@kroah.com>
References: <20220823080117.738248512@linuxfoundation.org>
 <20221026160051.5340-1-mdecandia@gmail.com>
 <Y1ljluiq8Ojp4vdL@kroah.com>
 <CAAPDZK9Oz2Hs9wofW9820gM=SeWgycCEWN=Xsjmy-YY_iFBcfQ@mail.gmail.com>
 <CALvZod5My-JaXBSm1iuVSFMiarB2YuE=O0AxD=6ZG0BfmJZ1AQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALvZod5My-JaXBSm1iuVSFMiarB2YuE=O0AxD=6ZG0BfmJZ1AQ@mail.gmail.com>
Precedence: bulk

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@gmail.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