From: kbuild test robot <lkp@intel.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: kbuild-all@01.org, Mark Fasheh <mfasheh@suse.com>,
Joel Becker <jlbec@evilplan.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
ocfs2-devel@oss.oracle.com,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Ryan Ding <ryan.ding@oracle.com>
Subject: Re: [PATCH] ocfs2: fix build warning
Date: Sun, 14 Feb 2016 06:45:17 +0800 [thread overview]
Message-ID: <201602140629.TOXLsDUG%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454395613-3428-1-git-send-email-sudipm.mukherjee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
Hi Sudip,
[auto build test ERROR on v4.5-rc2]
[cannot apply to next-20160212]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Sudip-Mukherjee/ocfs2-fix-build-warning/20160202-144936
config: i386-randconfig-x0-02140608 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/ocfs2/file.c: In function 'ocfs2_file_write_iter':
>> fs/ocfs2/file.c:2369:3: error: label 'relock' used but not defined
goto relock;
^
vim +/relock +2369 fs/ocfs2/file.c
9517bac6 Mark Fasheh 2007-02-09 2363 rw_level = -1;
9517bac6 Mark Fasheh 2007-02-09 2364
9517bac6 Mark Fasheh 2007-02-09 2365 direct_io = 0;
7da839c4 Al Viro 2015-04-09 2366 iocb->ki_flags &= ~IOCB_DIRECT;
3309dd04 Al Viro 2015-04-09 2367 iov_iter_reexpand(from, orig_count);
7da839c4 Al Viro 2015-04-09 2368 dropped_dio = 1;
9517bac6 Mark Fasheh 2007-02-09 @2369 goto relock;
9517bac6 Mark Fasheh 2007-02-09 2370 }
9517bac6 Mark Fasheh 2007-02-09 2371
a11f7e63 Mark Fasheh 2011-06-22 2372 if (unaligned_dio) {
:::::: The code at line 2369 was first introduced by commit
:::::: 9517bac6cc7a7aa4fee63cb38a32cb6014e264c7 ocfs2: teach ocfs2_file_aio_write() about sparse files
:::::: TO: Mark Fasheh <mark.fasheh@oracle.com>
:::::: CC: Mark Fasheh <mark.fasheh@oracle.com>
---
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: 19962 bytes --]
prev parent reply other threads:[~2016-02-13 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 6:46 Sudip Mukherjee
2016-02-02 8:01 ` Ryan Ding
2016-02-13 22:45 ` kbuild test robot [this message]
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=201602140629.TOXLsDUG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=ryan.ding@oracle.com \
--cc=sudipm.mukherjee@gmail.com \
/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®