Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp3060432ybh; Mon, 5 Aug 2019 11:17:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqxPA/huclr0JXJAja2WNItLw/RIjvpd+hfpAo2fibZWq3dnC44I/6QjqWuUTIC6a/MhwoAL X-Received: by 2002:a17:902:740a:: with SMTP id g10mr146743140pll.82.1565029058166; Mon, 05 Aug 2019 11:17:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565029058; cv=none; d=google.com; s=arc-20160816; b=P6BOToGbApqpcL5pL46tbuXREfOWBTBA3KjmYaJZtv+kLhBXgcK9VTYTvz3lCVa/JJ YHYpoFACKCDWAcG8W5T7u3fHHwu5H4GUuirGxUHxmb73MaWybzcyEHh5VC0UqQBSMdz3 Yu90smypnuPXD+D2PhmJob8phsjcVmGtVLJ/thFmNrHyey4wAgae0YzEOLyIUDFj0L23 HSwya1oMkAcVP5lcmNka88LmjtCj+Py0/XomsaSyo4onTFojrPimkq9MzpM7yNAdHx7U BocG4Zt+Z3fIFr+ILvwoj/meo6kYwi+0ipXz79YIxVo2omkNLvxNf/YoZ5Y4cPnAjHqa jg3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :reply-to:message-id:subject:cc:to:from:date; bh=RQrWmppSlFL4frE+lcQ3/iI00qwqAnTQyvvOuidHWs8=; b=es5b2+0VdW+G3PPJwc2ddZrYzMeMvWn14DzfBmTarN4hJZ9EWddzvH6oYF2ZvSso8E MP0dLahIT+C3Diue8sd+tqBxSWqM/1avCLK0MN9ykOBJeQLhJpberHjrjb4hNv0yStZR 1V5aPQDapghscsmOYg+N9i8EakPFwqNPHYSfzTukoefrmvlvqxuSLC9ngMl4pWySCgWM iTpdd299iFNIM9HDpND+puMJQ2+YIdBN34MUeDvOg6Y9jow0j87D7EJKO9JGe2HYmccz VIcQdYlc69BSn/rnIBMPdgItCuotQAlkCBca6L13T5+Zl+YxdpCH9pMEPFhNO0kcwPsA rYXw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u91si22806530plb.243.2019.08.05.11.17.22; Mon, 05 Aug 2019 11:17:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729765AbfHESQm (ORCPT + 99 others); Mon, 5 Aug 2019 14:16:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:56848 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727802AbfHESQm (ORCPT ); Mon, 5 Aug 2019 14:16:42 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id E4035AC91; Mon, 5 Aug 2019 18:16:40 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 4623DDABC7; Mon, 5 Aug 2019 20:17:13 +0200 (CEST) Date: Mon, 5 Aug 2019 20:17:12 +0200 From: David Sterba To: Nathan Chancellor Cc: Nikolay Borisov , linux-btrfs@vger.kernel.org, paulmck@linux.ibm.com, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] btrfs: Hook btrfs' DRW lock to locktorture infrastructure Message-ID: <20190805181712.GH28208@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Nathan Chancellor , Nikolay Borisov , linux-btrfs@vger.kernel.org, paulmck@linux.ibm.com, linux-kernel@vger.kernel.org References: <20190719083949.5351-1-nborisov@suse.com> <20190719084808.5877-1-nborisov@suse.com> <20190805163621.GA94502@archlinux-threadripper> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190805163621.GA94502@archlinux-threadripper> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 05, 2019 at 09:36:21AM -0700, Nathan Chancellor wrote: > Looks like this is in next-20190805 and causes a link time error when > CONFIG_BTRFS_FS is unset: > > LD vmlinux.o > MODPOST vmlinux.o > MODINFO modules.builtin.modinfo > ld.lld: error: undefined symbol: btrfs_drw_lock_init > >>> referenced by locktorture.c > >>> locking/locktorture.o:(torture_drw_init) in archive kernel/built-in.a > > ld.lld: error: undefined symbol: btrfs_drw_write_lock > >>> referenced by locktorture.c > >>> locking/locktorture.o:(torture_drw_write_lock) in archive kernel/built-in.a > > ld.lld: error: undefined symbol: btrfs_drw_write_unlock > >>> referenced by locktorture.c > >>> locking/locktorture.o:(torture_drw_write_unlock) in archive kernel/built-in.a > > ld.lld: error: undefined symbol: btrfs_drw_read_lock > >>> referenced by locktorture.c > >>> locking/locktorture.o:(torture_drw_read_lock) in archive kernel/built-in.a > > ld.lld: error: undefined symbol: btrfs_drw_read_unlock > >>> referenced by locktorture.c > >>> locking/locktorture.o:(torture_drw_read_unlock) in archive kernel/built-in.a > > If this commit is to remain around, there should probably be static > inline stubs in fs/btrfs/locking.h. Apologies if this has already been > reported, I still see the commit in the btrfs for-next branch. Sorry for the build breakage, the patch is not essential for the patchset so I'll remove it from the upcoming for-next branch.