From: "lijunlong at openresty dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/28184] task_fd_lookup failed on linux 5.11
Date: Fri, 06 Aug 2021 02:25:37 +0000 [thread overview]
Message-ID: <bug-28184-6586-7qfHI2LO8D@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28184-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28184
lijunlong <lijunlong at openresty dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #13593|0 |1
is obsolete| |
--- Comment #3 from lijunlong <lijunlong at openresty dot com> ---
Created attachment 13595
--> https://sourceware.org/bugzilla/attachment.cgi?id=13595&action=edit
detect api files_lookup_fd_raw
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-08-06 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 2:47 [Bug tapsets/28184] New: " lijunlong at openresty dot com
2021-08-05 2:55 ` [Bug tapsets/28184] " lijunlong at openresty dot com
2021-08-05 2:56 ` lijunlong at openresty dot com
2021-08-06 2:25 ` lijunlong at openresty dot com [this message]
2021-08-19 18:02 ` scox at redhat dot com
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=bug-28184-6586-7qfHI2LO8D@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).