From: kbuild test robot <lkp@intel.com>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: kbuild-all@01.org, Boaz Harrosh <boaz@plexistor.com>,
Boaz Harrosh <ooo@electrozaur.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Boaz Harrosh <boazh@netapp.com>
Subject: Re: [PATCH 13/16] zuf: More file operation
Date: Tue, 13 Aug 2019 19:32:21 +0800 [thread overview]
Message-ID: <201908131907.myPGzzDn%lkp@intel.com> (raw)
In-Reply-To: <20190812164244.15580-14-boazh@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 3782 bytes --]
Hi Boaz,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3-rc4 next-20190813]
[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/Boaz-Harrosh/zuf-ZUFS-Zero-copy-User-mode-FileSystem/20190813-074124
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.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@intel.com>
All warnings (new ones prefixed by >>):
fs/zuf/file.c: In function 'zuf_fiemap':
>> fs/zuf/file.c:324:1: warning: the frame size of 8512 bytes is larger than 8192 bytes [-Wframe-larger-than=]
}
^
vim +324 fs/zuf/file.c
243
244 static int zuf_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
245 u64 offset, u64 len)
246 {
247 struct super_block *sb = inode->i_sb;
248 struct zuf_inode_info *zii = ZUII(inode);
249 struct zufs_ioc_fiemap ioc_fiemap = {
250 .hdr.operation = ZUFS_OP_FIEMAP,
251 .hdr.in_len = sizeof(ioc_fiemap),
252 .hdr.out_len = sizeof(ioc_fiemap),
253 .zus_ii = zii->zus_ii,
254 .start = offset,
255 .length = len,
256 .flags = fieinfo->fi_flags,
257 };
258 struct page *pages[ZUS_API_MAP_MAX_PAGES];
259 uint nump = 0, extents_max = 0;
260 int i, err;
261
262 zuf_dbg_vfs("[%ld] offset=0x%llx len=0x%llx extents_max=%u flags=0x%x\n",
263 inode->i_ino, offset, len, fieinfo->fi_extents_max,
264 fieinfo->fi_flags);
265
266 /* TODO: Have support for FIEMAP_FLAG_XATTR */
267 err = fiemap_check_flags(fieinfo, FIEMAP_FLAG_SYNC);
268 if (unlikely(err))
269 return err;
270
271 if (likely(fieinfo->fi_extents_max)) {
272 ulong start = (ulong)fieinfo->fi_extents_start;
273 ulong len = fieinfo->fi_extents_max *
274 sizeof(struct fiemap_extent);
275 ulong offset = start & (PAGE_SIZE - 1);
276 ulong end_offset = (offset + len) & (PAGE_SIZE - 1);
277 ulong __len;
278 uint nump_r;
279
280 nump = md_o2p_up(offset + len);
281 if (ARRAY_SIZE(pages) < nump) {
282 nump = ARRAY_SIZE(pages);
283 end_offset = 0;
284 }
285
286 nump_r = get_user_pages_fast(start, nump, WRITE, pages);
287 if (unlikely(nump != nump_r))
288 return -EFAULT;
289
290 __len = nump * PAGE_SIZE - offset;
291 if (end_offset)
292 __len -= (PAGE_SIZE - end_offset);
293
294 extents_max = __len / sizeof(struct fiemap_extent);
295
296 ioc_fiemap.hdr.len = extents_max * sizeof(struct fiemap_extent);
297 ioc_fiemap.hdr.offset = offset;
298 }
299 ioc_fiemap.extents_max = extents_max;
300
301 zuf_r_lock(zii);
302
303 err = zufc_dispatch(ZUF_ROOT(SBI(sb)), &ioc_fiemap.hdr, pages, nump);
304 if (unlikely(err)) {
305 zuf_dbg_err("zufs_dispatch failed => %d\n", err);
306 goto out;
307 }
308
309 fieinfo->fi_extents_mapped = ioc_fiemap.extents_mapped;
310 if (unlikely(extents_max &&
311 (extents_max < ioc_fiemap.extents_mapped))) {
312 zuf_err("extents_max=%d extents_mapped=%d\n", extents_max,
313 ioc_fiemap.extents_mapped);
314 err = -EINVAL;
315 }
316
317 out:
318 zuf_r_unlock(zii);
319
320 for (i = 0; i < nump; ++i)
321 put_page(pages[i]);
322
323 return err;
> 324 }
325
---
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: 69489 bytes --]
next prev parent reply other threads:[~2019-08-13 11:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 16:42 [PATCHSET 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-08-12 16:42 ` [PATCH 01/16] fs: Add the ZUF filesystem to the build + License Boaz Harrosh
2019-08-12 16:42 ` [PATCH 02/16] MAINTAINERS: Add the ZUFS maintainership Boaz Harrosh
2019-08-12 16:42 ` [PATCH 03/16] zuf: Preliminary Documentation Boaz Harrosh
2019-08-12 16:42 ` [PATCH 04/16] zuf: zuf-rootfs Boaz Harrosh
2019-08-12 16:42 ` [PATCH 05/16] zuf: zuf-core The ZTs Boaz Harrosh
2019-08-13 3:24 ` kbuild test robot
2019-08-13 10:18 ` Boaz Harrosh
2019-08-13 5:06 ` kbuild test robot
2019-08-12 16:42 ` [PATCH 06/16] zuf: Multy Devices Boaz Harrosh
2019-08-13 8:11 ` kbuild test robot
2019-08-13 10:25 ` Boaz Harrosh
2019-08-12 16:42 ` [PATCH 07/16] zuf: mounting Boaz Harrosh
2019-08-13 8:58 ` kbuild test robot
2019-08-12 16:42 ` [PATCH 08/16] zuf: Namei and directory operations Boaz Harrosh
2019-08-12 16:42 ` [PATCH 09/16] zuf: readdir operation Boaz Harrosh
[not found] ` <201908131749.N9ibirdS%lkp@intel.com>
2019-08-13 10:26 ` Boaz Harrosh
2019-08-12 16:42 ` [PATCH 10/16] zuf: symlink Boaz Harrosh
2019-08-12 16:42 ` [PATCH 11/16] zuf: Write/Read implementation Boaz Harrosh
2019-08-13 10:23 ` kbuild test robot
2019-08-13 10:28 ` Boaz Harrosh
2019-08-12 16:42 ` [PATCH 12/16] zuf: mmap & sync Boaz Harrosh
2019-08-12 16:42 ` [PATCH 13/16] zuf: More file operation Boaz Harrosh
2019-08-13 11:32 ` kbuild test robot [this message]
2019-08-12 16:42 ` [PATCH 14/16] zuf: ioctl implementation Boaz Harrosh
2019-08-12 16:42 ` [PATCH 15/16] zuf: xattr && acl implementation Boaz Harrosh
2019-08-12 16:42 ` [PATCH 16/16] zuf: Support for dynamic-debug of zusFSs Boaz Harrosh
2019-08-12 16:47 [PATCHSET 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-08-12 16:48 ` [PATCH 13/16] zuf: More file operation Boaz Harrosh
2019-09-26 2:07 [PATCHSET v02 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-09-26 2:07 ` [PATCH 13/16] zuf: More file operation Boaz Harrosh
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=201908131907.myPGzzDn%lkp@intel.com \
--to=lkp@intel.com \
--cc=boaz@plexistor.com \
--cc=boazh@netapp.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ooo@electrozaur.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;
as well as URLs for NNTP newsgroup(s).