All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Desmond Cheong Zhi Xi" <desmondcheongzx@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: address potential UAF bugs with drm_master ptrs (rev3)
Date: Wed, 30 Jun 2021 17:38:57 -0000	[thread overview]
Message-ID: <162507473722.10375.5690477082283150812@emeril.freedesktop.org> (raw)
In-Reply-To: <20210629033706.20537-1-desmondcheongzx@gmail.com>

== Series Details ==

Series: drm: address potential UAF bugs with drm_master ptrs (rev3)
URL   : https://patchwork.freedesktop.org/series/91969/
State : failure

== Summary ==

Applying: drm: avoid circular locks in drm_mode_getconnector
Applying: drm: add a locked version of drm_is_current_master
Applying: drm: protect drm_master pointers in drm_lease.c
error: git diff header lacks filename information when removing 1 leading pathname component (line 2)
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0003 drm: protect drm_master pointers in drm_lease.c
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2021-06-30 17:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  3:37 [PATCH v5 0/3] drm: address potential UAF bugs with drm_master ptrs Desmond Cheong Zhi Xi
2021-06-29  3:37 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-29  3:37 ` Desmond Cheong Zhi Xi
2021-06-29  3:37 ` Desmond Cheong Zhi Xi
2021-06-29  3:37 ` [PATCH v5 1/3] drm: avoid circular locks in drm_mode_getconnector Desmond Cheong Zhi Xi
2021-06-29  3:37   ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-29  3:37   ` Desmond Cheong Zhi Xi
2021-06-29  3:37   ` Desmond Cheong Zhi Xi
2021-06-29  3:37 ` [PATCH v5 2/3] drm: add a locked version of drm_is_current_master Desmond Cheong Zhi Xi
2021-06-29  3:37   ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-29  3:37   ` Desmond Cheong Zhi Xi
2021-06-29  3:37   ` Desmond Cheong Zhi Xi
2021-06-29  3:37 ` [PATCH v5 3/3] drm: protect drm_master pointers in drm_lease.c Desmond Cheong Zhi Xi
2021-06-29  3:37   ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-29  3:37   ` Desmond Cheong Zhi Xi
2021-06-29  3:37   ` Desmond Cheong Zhi Xi
2021-06-29 16:07   ` Daniel Vetter
2021-06-29 16:07     ` [Intel-gfx] " Daniel Vetter
2021-06-29 16:07     ` Daniel Vetter
2021-06-29 16:07     ` Daniel Vetter
2021-06-30  7:18     ` Desmond Cheong Zhi Xi
2021-06-30  7:18       ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-30  7:18       ` Desmond Cheong Zhi Xi
2021-06-30  8:02       ` Daniel Vetter
2021-06-30  8:02         ` [Intel-gfx] " Daniel Vetter
2021-06-30  8:02         ` Daniel Vetter
2021-06-30  8:02         ` Daniel Vetter
2021-06-30 10:39         ` Desmond Cheong Zhi Xi
2021-06-30 10:39           ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-30 10:39           ` Desmond Cheong Zhi Xi
2021-06-30 10:39           ` Desmond Cheong Zhi Xi
2021-06-30  0:16   ` Emil Velikov
2021-06-30  0:16     ` [Intel-gfx] " Emil Velikov
2021-06-30  0:16     ` Emil Velikov
2021-06-30  0:16     ` Emil Velikov
2021-06-30  6:37     ` Desmond Cheong Zhi Xi
2021-06-30  6:37       ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-06-30  6:37       ` Desmond Cheong Zhi Xi
2021-06-30  6:37       ` Desmond Cheong Zhi Xi
2021-06-29 17:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: address potential UAF bugs with drm_master ptrs (rev2) Patchwork
2021-06-29 17:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-29 22:38 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-30 17:38 ` Patchwork [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=162507473722.10375.5690477082283150812@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=desmondcheongzx@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.