From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw139066 [PATCH] vhost: fix crash caused by accessing a freed vsocket
Date: Wed, 03 Apr 2024 00:14:27 -0700 (PDT) [thread overview]
Message-ID: <660d01d3.050a0220.d0362.8384SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <TYAP286MB0649588660B26F0CC783BAABD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/139066
_apply patch failure_
Submitter: Gongming Chen <chengongming1900@outlook.com>
Date: Wednesday, April 03 2024 02:57:18
Applied on: CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
Apply patch set 139066 failed:
Cloning the DPDK mirror at: https://github.com/DPDK/dpdk.git (Attempt 1 of 3)
Trying to checkout branch: origin/main
Checked out to main (e2e546ab5bf5e024986ccb5310ab43982f3bb40c)
Done: main commit e2e546ab5bf5e024986ccb5310ab43982f3bb40c
Trying to checkout branch: origin/next-virtio-for-next-net
Checked out to next-virtio-for-next-net (deedfb86a7a6e10064d3cccd593f62072de96e36)
Applying patch...
Failed to apply patch:
Applying: vhost: fix crash caused by accessing a freed vsocket
error: patch failed: lib/vhost/fd_man.c:250
error: lib/vhost/fd_man.c: patch does not apply
error: patch failed: lib/vhost/socket.c:463
error: lib/vhost/socket.c: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch' to see the failed patch
Using index info to reconstruct a base tree...
Patch failed at 0001 vhost: fix crash caused by accessing a freed vsocket
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".
Trying to checkout branch: origin/main
Checked out to main (e2e546ab5bf5e024986ccb5310ab43982f3bb40c)
Applying patch...
Failed to apply patch:
Applying: vhost: fix crash caused by accessing a freed vsocket
error: patch failed: lib/vhost/fd_man.c:250
error: lib/vhost/fd_man.c: patch does not apply
error: patch failed: lib/vhost/socket.c:463
error: lib/vhost/socket.c: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch' to see the failed patch
Using index info to reconstruct a base tree...
Patch failed at 0001 vhost: fix crash caused by accessing a freed vsocket
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".
https://lab.dpdk.org/results/dashboard/patchsets/29697/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2024-04-03 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYAP286MB0649588660B26F0CC783BAABD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-04-03 2:43 ` qemudev
2024-04-03 2:59 ` checkpatch
2024-04-03 7:14 ` dpdklab [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=660d01d3.050a0220.d0362.8384SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.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 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).