From: Daeho Jeong <daeho.jeong@samsung.com>
To: kbuild test robot <lkp@intel.com>,
"tytso@mit.edu" <tytso@mit.edu>, "jack@suse.cz" <jack@suse.cz>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
daeho.jeong@samsung.com
Subject: Re: [PATCH v2 2/3] ext4: fix races between changing inode journal mode and ext4_writepages
Date: Wed, 02 Mar 2016 01:21:35 +0000 (GMT) [thread overview]
Message-ID: <199292570.46101456881693870.JavaMail.weblogic@ep2mlwas09c> (raw)
Oops, This build error log is genereated when building ext4 filesystem as a module and
this is originated from that "percpu_free_rwsem()" function was not defined as an exported
function.
Could I define the "percpu_free_rwsem()" function as an exported function directly in this patch?
Or do I have to request the maintainer of percpu_rwsem to do this?
Thank you in advance. :-)
> url: https://github.com/0day-ci/linux/commits/Daeho-Jeong/ext4-handle-unwritten-or-delalloc-buffers-before-enabling-per-file-dat> a-journaling/20160229-075117
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
> config: x86_64-randconfig-s2-02290828 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
> All errors (new ones prefixed by >>):
> >> ERROR: "percpu_free_rwsem" [fs/ext4/ext4.ko] undefined!
next reply other threads:[~2016-03-02 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 1:21 Daeho Jeong [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-28 23:48 [PATCH v2 1/3] ext4: handle unwritten or delalloc buffers before enabling per-file data journaling Daeho Jeong
2016-02-28 23:48 ` [PATCH v2 2/3] ext4: fix races between changing inode journal mode and ext4_writepages Daeho Jeong
2016-02-29 1:29 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199292570.46101456881693870.JavaMail.weblogic@ep2mlwas09c \
--to=daeho.jeong@samsung.com \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).