From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for dma-buf: Flag vmap'ed memory as system or I/O memory (rev3)
Date: Fri, 25 Sep 2020 12:07:58 -0000 [thread overview]
Message-ID: <160103567807.10247.10549588760844646596@emeril.freedesktop.org> (raw)
In-Reply-To: <20200925115601.23955-1-tzimmermann@suse.de>
== Series Details ==
Series: dma-buf: Flag vmap'ed memory as system or I/O memory (rev3)
URL : https://patchwork.freedesktop.org/series/81647/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c94eaf86e18e dma-buf: Add struct dma-buf-map for storing struct dma_buf.vaddr_ptr
-:47: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#47: FILE: drivers/dma-buf/dma-buf.c:1212:
+ BUG_ON(dma_buf_map_is_null(&dmabuf->vmap_ptr));
-:53: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#53: FILE: drivers/dma-buf/dma-buf.c:1217:
+ BUG_ON(dma_buf_map_is_set(&dmabuf->vmap_ptr));
-:71: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#71: FILE: drivers/dma-buf/dma-buf.c:1244:
+ BUG_ON(dma_buf_map_is_null(&dmabuf->vmap_ptr));
-:74: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#74: FILE: drivers/dma-buf/dma-buf.c:1246:
+ BUG_ON(!dma_buf_map_is_vaddr(&dmabuf->vmap_ptr, vaddr));
-:86: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#86:
new file mode 100644
total: 0 errors, 5 warnings, 0 checks, 138 lines checked
55973e093508 dma-buf: Use struct dma_buf_map in dma_buf_vmap() interfaces
c929afc2d68f dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces
-:48: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#48: FILE: drivers/dma-buf/dma-buf.c:1250:
+ BUG_ON(!dma_buf_map_is_equal(&dmabuf->vmap_ptr, map));
total: 0 errors, 1 warnings, 0 checks, 287 lines checked
993652ae5805 dma-buf: Document struct dma_buf_map
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-09-25 12:08 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 11:55 [PATCH v3 0/4] dma-buf: Flag vmap'ed memory as system or I/O memory Thomas Zimmermann
2020-09-25 11:55 ` [Intel-gfx] " Thomas Zimmermann
2020-09-25 11:55 ` Thomas Zimmermann
2020-09-25 11:55 ` [PATCH v3 1/4] dma-buf: Add struct dma-buf-map for storing struct dma_buf.vaddr_ptr Thomas Zimmermann
2020-09-25 11:55 ` [Intel-gfx] " Thomas Zimmermann
2020-09-25 11:55 ` Thomas Zimmermann
2020-09-25 11:55 ` [PATCH v3 2/4] dma-buf: Use struct dma_buf_map in dma_buf_vmap() interfaces Thomas Zimmermann
2020-09-25 11:55 ` [Intel-gfx] " Thomas Zimmermann
2020-09-25 11:55 ` Thomas Zimmermann
2020-09-25 11:56 ` [PATCH v3 3/4] dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces Thomas Zimmermann
2020-09-25 11:56 ` [Intel-gfx] " Thomas Zimmermann
2020-09-25 11:56 ` Thomas Zimmermann
2020-09-25 11:56 ` [PATCH v3 4/4] dma-buf: Document struct dma_buf_map Thomas Zimmermann
2020-09-25 11:56 ` [Intel-gfx] " Thomas Zimmermann
2020-09-25 11:56 ` Thomas Zimmermann
2020-09-25 12:07 ` Patchwork [this message]
2020-09-25 12:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for dma-buf: Flag vmap'ed memory as system or I/O memory (rev3) Patchwork
2020-09-25 12:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-09-25 16:53 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-09-25 18:57 ` [PATCH v3 0/4] dma-buf: Flag vmap'ed memory as system or I/O memory Tomasz Figa
2020-09-25 18:57 ` [Intel-gfx] " Tomasz Figa
2020-09-25 18:57 ` Tomasz Figa
2020-09-26 7:13 ` Sam Ravnborg
2020-09-26 7:13 ` [Intel-gfx] " Sam Ravnborg
2020-09-26 7:13 ` Sam Ravnborg
2020-09-27 18:36 ` Thomas Zimmermann
2020-09-27 18:36 ` [Intel-gfx] " Thomas Zimmermann
2020-09-27 18:36 ` Thomas Zimmermann
2020-09-27 19:16 ` Sam Ravnborg
2020-09-27 19:16 ` [Intel-gfx] " Sam Ravnborg
2020-09-27 19:16 ` Sam Ravnborg
2020-09-28 6:50 ` Christian König
2020-09-28 6:50 ` [Intel-gfx] " Christian König
2020-09-28 6:50 ` Christian König
2020-09-28 7:37 ` Thomas Zimmermann
2020-09-28 7:37 ` [Intel-gfx] " Thomas Zimmermann
2020-09-28 7:37 ` Thomas Zimmermann
2020-09-28 11:22 ` Christian König
2020-09-28 11:22 ` [Intel-gfx] " Christian König
2020-09-28 11:22 ` Christian König
2020-09-29 9:14 ` Daniel Vetter
2020-09-29 9:14 ` [Intel-gfx] " Daniel Vetter
2020-09-29 9:14 ` Daniel Vetter
2020-09-29 11:09 ` Christian König
2020-09-29 11:09 ` [Intel-gfx] " Christian König
2020-09-29 11:09 ` Christian König
2020-09-29 11:14 ` Thomas Zimmermann
2020-09-29 11:14 ` [Intel-gfx] " Thomas Zimmermann
2020-09-29 11:14 ` Thomas Zimmermann
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=160103567807.10247.10549588760844646596@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.