mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Stanislav Kinsburskiy <skinsbursky@virtuozzo.com>
Cc: kbuild-all@01.org, bfields@fieldses.org, jlayton@poochiereds.net,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, devel@criu.org
Subject: Re: [PATCH] fcntl: allow to set O_DIRECT flag on pipe
Date: Wed, 16 Dec 2015 00:14:00 +0800	[thread overview]
Message-ID: <201512160020.glLSgrhW%fengguang.wu@intel.com> (raw)
In-Reply-To: <20151215151325.15499.65499.stgit@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]

Hi Stanislav,

[auto build test ERROR on v4.4-rc5]
[also build test ERROR on next-20151215]

url:    https://github.com/0day-ci/linux/commits/Stanislav-Kinsburskiy/fcntl-allow-to-set-O_DIRECT-flag-on-pipe/20151216-000234
config: x86_64-randconfig-x011-12141150 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   fs/fcntl.c: In function 'setfl':
>> fs/fcntl.c:55:7: error: implicit declaration of function 'IS_FIFO' [-Werror=implicit-function-declaration]
     if (!IS_FIFO(f->f_mode) && (arg & O_DIRECT)) {
          ^
>> fs/fcntl.c:55:15: error: 'f' undeclared (first use in this function)
     if (!IS_FIFO(f->f_mode) && (arg & O_DIRECT)) {
                  ^
   fs/fcntl.c:55:15: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors

vim +/IS_FIFO +55 fs/fcntl.c

    49		/* required for strict SunOS emulation */
    50		if (O_NONBLOCK != O_NDELAY)
    51		       if (arg & O_NDELAY)
    52			   arg |= O_NONBLOCK;
    53	
    54		/* Pipe packetized mode is controlled by O_DIRECT flag */
  > 55		if (!IS_FIFO(f->f_mode) && (arg & O_DIRECT)) {
    56			if (!filp->f_mapping || !filp->f_mapping->a_ops ||
    57				!filp->f_mapping->a_ops->direct_IO)
    58					return -EINVAL;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 21227 bytes --]

  reply	other threads:[~2015-12-15 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 15:14 Stanislav Kinsburskiy
2015-12-15 16:14 ` kbuild test robot [this message]
2015-12-15 16:15 ` 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=201512160020.glLSgrhW%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bfields@fieldses.org \
    --cc=devel@criu.org \
    --cc=jlayton@poochiereds.net \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skinsbursky@virtuozzo.com \
    --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

all inboxes | Powered by JetHome®