public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30416] unable to find member 'request' for struct scsi_cmnd
Date: Tue, 03 Oct 2023 19:18:46 +0000	[thread overview]
Message-ID: <bug-30416-6586-8DYDV8l8tF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30416-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30416

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
                 CC|                            |wcohen at redhat dot com

--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
This has been addressed by systemtap git commit
e94d0e3deb34e684ca83573d7d2bc9b382db2427

    Have the scsi tapset support newer kernels struct scsi_cmnd

    The linux kernel commit 2266a2def97ce11ec removed the request field
    from struct scsi_cmnd.  The scsi tapset needed to test whether the
    request field is available.  If request field is not available, use
    the linux kernels helper function scsi_cmd_to_rq to get a value for
    request.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2023-10-03 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  9:07 [Bug runtime/30416] New: " mcermak at redhat dot com
2023-10-03 19:18 ` wcohen at redhat dot com [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=bug-30416-6586-8DYDV8l8tF@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).