[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190624151217.GA249955@google.com>
Date: Mon, 24 Jun 2019 09:12:17 -0600
From: Ross Zwisler <zwisler@...gle.com>
To: kbuild test robot <lkp@...el.com>
Cc: Ross Zwisler <zwisler@...omium.org>, kbuild-all@...org,
linux-kernel@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Jan Kara <jack@...e.com>, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
Fletcher Woodruff <fletcherw@...gle.com>,
Justin TerAvest <teravest@...gle.com>, Jan Kara <jack@...e.cz>,
stable@...r.kernel.org
Subject: Re: [PATCH v2 3/3] ext4: use jbd2_inode dirty range scoping
On Mon, Jun 24, 2019 at 02:54:49AM +0800, kbuild test robot wrote:
> Hi Ross,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v5.2-rc6 next-20190621]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Ross-Zwisler/mm-add-filemap_fdatawait_range_keep_errors/20190623-181603
> config: x86_64-rhel-7.6 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@...el.com>
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "jbd2_journal_inode_ranged_wait" [fs/ext4/ext4.ko] undefined!
> >> ERROR: "jbd2_journal_inode_ranged_write" [fs/ext4/ext4.ko] undefined!
Yep, this is caused by the lack of EXPORT_SYMBOL() calls for these two new
jbd2 functions. Ted also pointed this out and fixed this up when he was
committing:
https://patchwork.kernel.org/patch/11007139/#22717091
Thank you for the report!
Powered by blists - more mailing lists