From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751444AbdK3WL3 (ORCPT ); Thu, 30 Nov 2017 17:11:29 -0500 Received: from verein.lst.de ([213.95.11.211]:32856 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750760AbdK3WL2 (ORCPT ); Thu, 30 Nov 2017 17:11:28 -0500 Date: Thu, 30 Nov 2017 23:11:26 +0100 From: Christoph Hellwig To: Jason Baron Cc: Andrew Morton , Christoph Hellwig , Ingo Molnar , Peter Zijlstra , Al Viro , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: waitqueue lockdep annotation Message-ID: <20171130221126.GA31795@lst.de> References: <20171130142037.19339-1-hch@lst.de> <20171130125050.1faba3f06fc572846f792f17@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 30, 2017 at 04:38:02PM -0500, Jason Baron wrote: > I don't think there is a bug here. The 'wake_up_locked()' calls in epoll > are being protected by the ep->lock, not the wait_queue_head lock. So > arguably the 'annotation' is wrong, but I don't think there is a bug > beyond that. They can't be protected by ep->lock. The file might as well be watched for using poll or select as well, or just using epoll using another epoll fd.