From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 68341C4363C for ; Sun, 4 Oct 2020 20:05:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2EEE82068E for ; Sun, 4 Oct 2020 20:05:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726300AbgJDUFe (ORCPT ); Sun, 4 Oct 2020 16:05:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38990 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726294AbgJDUFe (ORCPT ); Sun, 4 Oct 2020 16:05:34 -0400 Received: from ZenIV.linux.org.uk (zeniv.linux.org.uk [IPv6:2002:c35c:fd02::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 055DBC0613CE; Sun, 4 Oct 2020 13:05:33 -0700 (PDT) Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1kPAGB-00BwHH-Bg; Sun, 04 Oct 2020 20:05:31 +0000 Date: Sun, 4 Oct 2020 21:05:31 +0100 From: Al Viro To: Linus Torvalds Cc: Linux Kernel Mailing List , linux-fsdevel , Marc Zyngier Subject: Re: [RFC][PATCHSET] epoll cleanups Message-ID: <20201004200531.GR3421308@ZenIV.linux.org.uk> References: <20201004023608.GM3421308@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Al Viro Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Sun, Oct 04, 2020 at 11:08:11AM -0700, Linus Torvalds wrote: > On Sat, Oct 3, 2020 at 7:36 PM Al Viro wrote: > > > > Locking and especially control flow in fs/eventpoll.c is > > overcomplicated. As the result, the code has been hard to follow > > and easy to fuck up while modifying. > > Scanning through the patches they all look superficially ok to me, but > I'm wondering how much test coverage you have (because I'm wondering > how much test coverage we have in general for epoll). Besides the in-tree one (tools/testing/selftests/filesystems/epoll) and LTP stuff (testcases/kernel/syscalls/epoll) - only davidel's epoll_test.c. Plus slapped together "let's try to make it go through that codepath" stuff (combined with printks in fs/eventpoll.c)...