From: kbuild test robot <lkp@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:work.open3 37/44] fs/pipe.c:764:23: error: 'path' undeclared
Date: Thu, 12 Jul 2018 05:41:00 +0800 [thread overview]
Message-ID: <201807120554.7qSReRm6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3495 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.open3
head: c94be0673577f7373cf67bba317cef2db9094530
commit: 335331bef622bd232800d50c85b54056fa02d808 [37/44] create_pipe_files(): switch the first allocation to alloc_file_pseudo()
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
git checkout 335331bef622bd232800d50c85b54056fa02d808
# save the attached .config to linux build tree
make ARCH=i386
Note: the vfs/work.open3 HEAD c94be0673577f7373cf67bba317cef2db9094530 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
fs/pipe.c: In function 'create_pipe_files':
>> fs/pipe.c:764:23: error: 'path' undeclared (first use in this function)
res[0] = alloc_file(&path, O_RDONLY | (flags & O_NONBLOCK),
^~~~
fs/pipe.c:764:23: note: each undeclared identifier is reported only once for each function it appears in
vim +/path +764 fs/pipe.c
^1da177e Linus Torvalds 2005-04-16 744
e4fad8e5 Al Viro 2012-07-21 745 int create_pipe_files(struct file **res, int flags)
^1da177e Linus Torvalds 2005-04-16 746 {
e4fad8e5 Al Viro 2012-07-21 747 struct inode *inode = get_pipe_inode();
d6cbd281 Andi Kleen 2006-09-30 748 struct file *f;
^1da177e Linus Torvalds 2005-04-16 749
^1da177e Linus Torvalds 2005-04-16 750 if (!inode)
e4fad8e5 Al Viro 2012-07-21 751 return -ENFILE;
^1da177e Linus Torvalds 2005-04-16 752
335331be Al Viro 2018-06-09 753 f = alloc_file_pseudo(inode, pipe_mnt, "",
335331be Al Viro 2018-06-09 754 O_WRONLY | (flags & (O_NONBLOCK | O_DIRECT)),
12ec508a Al Viro 2018-07-11 755 &pipefifo_fops);
e9bb1f9b Eric Biggers 2015-10-17 756 if (IS_ERR(f)) {
335331be Al Viro 2018-06-09 757 free_pipe_info(inode->i_pipe);
335331be Al Viro 2018-06-09 758 iput(inode);
335331be Al Viro 2018-06-09 759 return PTR_ERR(f);
e9bb1f9b Eric Biggers 2015-10-17 760 }
341b446b Ingo Molnar 2006-04-11 761
de32ec4c Al Viro 2013-03-21 762 f->private_data = inode->i_pipe;
^1da177e Linus Torvalds 2005-04-16 763
12ec508a Al Viro 2018-07-11 @764 res[0] = alloc_file(&path, O_RDONLY | (flags & O_NONBLOCK),
12ec508a Al Viro 2018-07-11 765 &pipefifo_fops);
e9bb1f9b Eric Biggers 2015-10-17 766 if (IS_ERR(res[0])) {
b10a4a9f Al Viro 2018-07-09 767 put_pipe_info(inode, inode->i_pipe);
b10a4a9f Al Viro 2018-07-09 768 fput(f);
b10a4a9f Al Viro 2018-07-09 769 return PTR_ERR(res[0]);
e9bb1f9b Eric Biggers 2015-10-17 770 }
e4fad8e5 Al Viro 2012-07-21 771
335331be Al Viro 2018-06-09 772 path_get(&f->f_path);
de32ec4c Al Viro 2013-03-21 773 res[0]->private_data = inode->i_pipe;
e4fad8e5 Al Viro 2012-07-21 774 res[1] = f;
e4fad8e5 Al Viro 2012-07-21 775 return 0;
d6cbd281 Andi Kleen 2006-09-30 776 }
d6cbd281 Andi Kleen 2006-09-30 777
:::::: The code at line 764 was first introduced by commit
:::::: 12ec508a2586dcb99a9ec383b1b98057acb9fc02 alloc_file(): switch to passing O_... flags instead of FMODE_... mode
:::::: TO: Al Viro <viro@zeniv.linux.org.uk>
:::::: CC: Al Viro <viro@zeniv.linux.org.uk>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6370 bytes --]
reply other threads:[~2018-07-11 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201807120554.7qSReRm6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).