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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 A7B48C33C8C for ; Mon, 6 Jan 2020 17:51:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7279320715 for ; Mon, 6 Jan 2020 17:51:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lixom-net.20150623.gappssmtp.com header.i=@lixom-net.20150623.gappssmtp.com header.b="jzrof668" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726643AbgAFRv7 (ORCPT ); Mon, 6 Jan 2020 12:51:59 -0500 Received: from mail-io1-f68.google.com ([209.85.166.68]:34042 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726448AbgAFRv6 (ORCPT ); Mon, 6 Jan 2020 12:51:58 -0500 Received: by mail-io1-f68.google.com with SMTP id z193so49477038iof.1 for ; Mon, 06 Jan 2020 09:51:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qy8kmkp8a0gmcpulrYZGNAm7gLvS5DkjoDa1dT+iaq8=; b=jzrof668V7p7TIEBZmcBr7HsXeQHx4Y/82FDTr/eUsL2QuB+qyXSDZPa7kUuOW4p4V aQDgWoEHRRaMXH2PbD5aNjNwR4/aok96ojD23mByECE8J/9RVT5Qxcx1m+Nzu+10gkjE SnmQYwRYzPnX9blWGY3RBLpqxH9HNLy2+U6YVhhVSoBfFvzZlepNx/ajOLI29PDltHmI GUn/LnnhMEFQquexorSKg8FbdHrsVah6Ucn5QZvBeqI9DkJiBJDMiXlIecF01kRGlfbz bmiJ6ex6i/ZJgeTsQQ9i//PmTbQha9ze3n/iSkJf1V1vwxHCqgjWmbnX7S2xll8o81aQ W21Q== 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=Qy8kmkp8a0gmcpulrYZGNAm7gLvS5DkjoDa1dT+iaq8=; b=gn7FJ7l0rBTgiP8jhWRx3FJYuLXhNFnzBS7351p0106ETu8a7+e6uz+M3koyYzf/HR J2gL2xRhtXN3gmsKh7IcwuMqEC+r8mC/YeaEUx1Jiizt1hD8nwt5tvHn48C9C2sQ5puP nFh8kJDB+8ER/Q4hXHDlSgNUcnNIw2wImleQnGU/qCYBTlq6sTRqPT53YnxCpBA3OQ13 jKaEOz1tUweWZBIJ4B4wry9GQA+ePk8mkRpqK07DpLS7fImh3O0iARqr3481vua5Qu1m NmHB/rJtCCx8MArA96ydy/pKLmI+N79OUwn5nnh7YaY4ba4J1oHq4CDuUtCcT9O6w8OP Jiow== X-Gm-Message-State: APjAAAVZRNOa1LETD7UT2ewkLTkh9PxWE7t+T7CdSiH7xbVX70u3vfmT 4snn9gKwJHtpI6ABIWj0IVH3js/5L2Ow6C0GUb332w== X-Google-Smtp-Source: APXvYqzxsugGn2yxQHaeUuSSUV2TAe/3zs6sdz/iqVons8XXpedlHaNhKZESuFkh1KRYRsPmdvlmPUWnayfpHU/1dgI= X-Received: by 2002:a5e:9907:: with SMTP id t7mr69813324ioj.72.1578333118209; Mon, 06 Jan 2020 09:51:58 -0800 (PST) MIME-Version: 1.0 References: <20191212160622.021517d3@canb.auug.org.au> In-Reply-To: <20191212160622.021517d3@canb.auug.org.au> From: Olof Johansson Date: Mon, 6 Jan 2020 09:51:47 -0800 Message-ID: Subject: Re: linux-next: build warning after merge of the rcu tree To: Stephen Rothwell Cc: "Paul E. McKenney" , Linux Next Mailing List , Linux Kernel Mailing List , Eric Dumazet Content-Type: text/plain; charset="UTF-8" Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org Hi, On Wed, Dec 11, 2019 at 9:06 PM Stephen Rothwell wrote: > > Hi all, > > After merging the rcu (I think) tree, today's linux-next build (x86_64 > allnoconfig) produced this warning: > > kernel/time/timer.c: In function 'schedule_timeout': > kernel/time/timer.c:969:20: warning: 'timer.expires' may be used uninitialized in this function [-Wmaybe-uninitialized] > 969 | long diff = timer->expires - expires; > | ~~~~~^~~~~~~~~ > > Introduced by (bisected to) commit > > c4127fce1d02 ("timer: Use hlist_unhashed_lockless() in timer_pending()") > > x86_64-linux-gnu-gcc (Debian 9.2.1-21) 9.2.1 20191130 This is still there as of last night's -next. Any update on getting a fix queued together with the offending patch? Thanks! -Olof