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=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 53718C282DC for ; Sun, 2 Jun 2019 12:20:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2903321670 for ; Sun, 2 Jun 2019 12:20:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=joelfernandes.org header.i=@joelfernandes.org header.b="cpm9Wahq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726683AbfFBMU2 (ORCPT ); Sun, 2 Jun 2019 08:20:28 -0400 Received: from mail-lf1-f65.google.com ([209.85.167.65]:33715 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726387AbfFBMU2 (ORCPT ); Sun, 2 Jun 2019 08:20:28 -0400 Received: by mail-lf1-f65.google.com with SMTP id y17so11419318lfe.0 for ; Sun, 02 Jun 2019 05:20:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=P8XJjbcSeHXWyfrm0lZNaxFevNGN/ntRWhil7kOzvQw=; b=cpm9Wahqojbpp4VkjWfrSzKQi0a2ao6+Snhc7Rw0Q7G2cnlWl4NN+SpMBNDiynHStQ e+MwKcJW+v+aBPTP2CMVHQ+2Z75W4hXURUexykVjLm+sx6J//Q5pTVNwqTtc92n26m9x wUI8z1LDwo3dz8mT0g1ckf93t0vtaHtsUBp88= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=P8XJjbcSeHXWyfrm0lZNaxFevNGN/ntRWhil7kOzvQw=; b=bHCzXZZ7sV8o6thT+/ZTeQQ4hz4LlU88Tvenpzyra8ngCjB3l1/+aLH8NfyqAPjy5c jQGpnEgKM/AEYh8k8zrogKebfKc50q8Ug6tp0yE6KYCpZ64Mx2UyPNGnbVdIuce2U3tw VKGbfZ+gW5nDljJwSGVWEOXx55CGQtRkp8S4tluBvVJxtJyKaRYS/lJ6yoObyl5fn98M e1nBih4hEjtNIhBgbLqpL6c3QlEpEF/AVg6DATY7tqksGs2s5KIYyrW+PA9TNqVNX+Bx L+ZPChyTbIWElvjlyne/clRO5vMQSsJQcgb41jBAw4CnVYSYFLurIBkucPP0Ns2pJlfd 4RTA== X-Gm-Message-State: APjAAAVlhAmGHRFiXS1Gv5pVeMn67WX4EA7Xwg28phdvFTpAf4KVxv94 Nt8szubW6Yqh/dYdf73Sby30ehI2d1X+iCgdcsLcRg== X-Google-Smtp-Source: APXvYqxoUeTRSI6CtltHxEsRlYpiPonozfm3ENUzJsZRTMHK2FWCrZ71nbqlV68IH4IhR7parmAXCyudOrYXvzl+KNs= X-Received: by 2002:ac2:4544:: with SMTP id j4mr10895112lfm.176.1559478026242; Sun, 02 Jun 2019 05:20:26 -0700 (PDT) MIME-Version: 1.0 References: <20190601222738.6856-1-joel@joelfernandes.org> <20190601222738.6856-3-joel@joelfernandes.org> <20190602070014.GA543@amd> In-Reply-To: <20190602070014.GA543@amd> From: Joel Fernandes Date: Sun, 2 Jun 2019 08:20:15 -0400 Message-ID: Subject: Re: [RFC 2/6] ipv4: add lockdep condition to fix for_each_entry To: Pavel Machek Cc: LKML , Alexey Kuznetsov , Bjorn Helgaas , Borislav Petkov , "David S. Miller" , Eric Dumazet , Greg Kroah-Hartman , Hideaki YOSHIFUJI , "H. Peter Anvin" , Ingo Molnar , Josh Triplett , Kees Cook , Kernel Hardening , Lai Jiangshan , Len Brown , linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org, Linux PM , Mathieu Desnoyers , Neil Brown , netdev , Oleg Nesterov , "Paul E. McKenney" , Peter Zilstra , "Rafael J. Wysocki" , rcu , Steven Rostedt , Tejun Heo , Thomas Gleixner , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" Content-Type: text/plain; charset="UTF-8" Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Sun, Jun 2, 2019 at 3:00 AM Pavel Machek wrote: > > On Sat 2019-06-01 18:27:34, Joel Fernandes (Google) wrote: > > Signed-off-by: Joel Fernandes (Google) > > This really needs to be merged to previous patch, you can't break > compilation in middle of series... > > Or probably you need hlist_for_each_entry_rcu_lockdep() macro with > additional argument, and switch users to it. Good point. I can also just add a temporary transition macro, and then remove it in the last patch. That way no new macro is needed. Thanks!