linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 215447] New: sr_mod scsi_mode_sense() failure -> "scsi-1 drive"
Date: Mon, 03 Jan 2022 18:00:39 +0000	[thread overview]
Message-ID: <bug-215447-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=215447

            Bug ID: 215447
           Summary: sr_mod scsi_mode_sense() failure -> "scsi-1 drive"
           Product: SCSI Drivers
           Version: 2.5
    Kernel Version: 5.15.6
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: scsi_drivers-other@kernel-bugs.osdl.org
          Reporter: cshorler@googlemail.com
        Regression: No

Created attachment 300216
  --> https://bugzilla.kernel.org/attachment.cgi?id=300216&action=edit
SUSE Tumbleweed default kernel with CONFIG_FUSION_LOGGING (debug_level 0x488)

scsi_lib.c: scsi_mode_sense() has defaults assuming MODE_SENSE_10, fallback to
MODE_SENSE if that fails.

sr.c: doesn't set sdev->use_10_for_ms.  In my case this causes
scsi_mode_sense() to fail and "scsi-1 drive" fallback to be selected.

I tried setting use_10_for_ms in the sr_probe() function, seems to work for
code page 0x2A, as requested by sr.c.

I'm unsure where the request for code page 0x19 originates / if failure is
acceptable or if it indicates another issue.

4 attachments

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-01-03 18:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 18:00 bugzilla-daemon [this message]
2022-01-03 18:03 ` [Bug 215447] sr_mod scsi_mode_sense() failure -> "scsi-1 drive" bugzilla-daemon
2022-01-03 18:04 ` bugzilla-daemon
2022-01-03 18:05 ` bugzilla-daemon
2022-01-15 11:42 ` bugzilla-daemon
2022-01-15 12:16   ` Christopher Horler
2022-01-15 13:08     ` Martin K. Petersen
2022-01-15 12:17 ` bugzilla-daemon
2022-01-15 13:08 ` bugzilla-daemon
2022-01-15 14:04 ` bugzilla-daemon
2022-01-19  4:02   ` Martin K. Petersen
2022-01-19  4:02 ` bugzilla-daemon
2022-01-19 21:20 ` bugzilla-daemon
2022-06-30 17:19 ` bugzilla-daemon

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-215447-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.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).