linux-kernel - megaraid sas driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 8 Apr 2008 13:41:58 -0700 (PDT)
From:	Rakesh <raksac@...oo.com>
To:	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	megaraidlinux@....com
Subject: megaraid sas driver

I am curious to ask, why were these lines omitted from
the megaraid SAS driver with kernel version 2.6.15
onwards.

In my opinion these were blocking physical disks which
were part of a RAID set on the controller from being
visible to OS. Is this correct?

Thanks,
Rakesh

----------------
megaraid_sas.c
                /*
 989                 * Don't export physical disk
devices to mid-layer.
 990                 */
 991                if (!MEGASAS_IS_LOGICAL(cmd->scmd)
&&
 992                    (hdr->cmd_status ==
MFI_STAT_OK) &&
 993                    (cmd->scmd->cmnd[0] ==
INQUIRY)) {
 994
 995                        if (((*(u8 *)
cmd->scmd->request_buffer) & 0x1F) ==
 996                            TYPE_DISK) {
 997                                cmd->scmd->result
= DID_BAD_TARGET << 16;
 998                                exception = 1;
 999                        }
1000                }




      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/