linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 215788] arcmsr driver on kernel 5.16 and up fails to initialize ARC-1280ML RAID controller
Date: Tue, 05 Apr 2022 19:44:28 +0000	[thread overview]
Message-ID: <bug-215788-11613-7AgoF2qW7L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215788-11613@https.bugzilla.kernel.org/>

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

--- Comment #3 from Jernej Simončič (jernej-bugzilla.kernel@ena.si) ---
Done, it points at this commit:

e815d36548f01797ce381be8f0b74f4ba9befd15 is the first bad commit
commit e815d36548f01797ce381be8f0b74f4ba9befd15
Author: Damien Le Moal <damien.lemoal@wdc.com>
Date:   Wed Oct 27 11:22:20 2021 +0900

    scsi: sd: add concurrent positioning ranges support

    Add the sd_read_cpr() function to the sd scsi disk driver to discover
    if a device has multiple concurrent positioning ranges (i.e. multiple
    actuators on an HDD). The existence of VPD page B9h indicates if a
    device has multiple concurrent positioning ranges. The page content
    describes each range supported by the device.

    sd_read_cpr() is called from sd_revalidate_disk() and uses the block
    layer functions disk_alloc_independent_access_ranges() and
    disk_set_independent_access_ranges() to represent the set of actuators
    of the device as independent access ranges.

    The format of the Concurrent Positioning Ranges VPD page B9h is defined
    in section 6.6.6 of SBC-5.

    Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Keith Busch <kbusch@kernel.org>
    Link:
https://lore.kernel.org/r/20211027022223.183838-3-damien.lemoal@wdc.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

 drivers/scsi/sd.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 drivers/scsi/sd.h |  1 +
 2 files changed, 82 insertions(+)

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

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

  parent reply	other threads:[~2022-04-06  1:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 10:50 [Bug 215788] New: arcmsr driver on kernel 5.16 and up fails to initialize ARC-1280ML RAID controller bugzilla-daemon
2022-04-01 11:00 ` [Bug 215788] " bugzilla-daemon
2022-04-02  7:56 ` bugzilla-daemon
2022-04-05  5:08 ` bugzilla-daemon
2022-04-05 19:44 ` bugzilla-daemon [this message]
2022-04-05 19:51 ` bugzilla-daemon
2022-04-05 23:29 ` bugzilla-daemon
2022-04-06  6:59 ` bugzilla-daemon
2022-04-06  8:26 ` bugzilla-daemon
2022-04-06 16:35 ` bugzilla-daemon
2022-04-06 16:43 ` bugzilla-daemon
2022-04-06 22:49 ` bugzilla-daemon
2022-04-07  4:01 ` bugzilla-daemon
2022-04-07  7:10 ` bugzilla-daemon
2022-04-07  7:20   ` Damien Le Moal
2022-04-07  7:18 ` bugzilla-daemon
2022-04-07  7:20 ` bugzilla-daemon
2022-04-21  6:52 ` bugzilla-daemon
2022-04-25  2:28 ` bugzilla-daemon
2022-04-25 14:17 ` bugzilla-daemon
2023-09-21 21:13 ` bugzilla-daemon
2023-09-22  8:32 ` bugzilla-daemon
2023-09-22 13:49 ` bugzilla-daemon
2023-09-22 17:28 ` 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-215788-11613-7AgoF2qW7L@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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).