>
> i.e., what is this binary blob (?)
>
> I don't see a binary blob in this patch (as stated in the first
> sentence). I'd say that this patch adds methods for exporting
> (or exposing) the ibft thru sysfs.
I used the wrong choice of words. The correct one is, as you say, to
add methods for exporting the iBFT through sysfs.
>
> Is there some good reason that the iSCSI connection information
> shouldn't be exposed in real sysfs attribute files instead of just
> in a binary file?
My end goal is to export the iBFT data via individual sysfs attribute files. I
was thinking to do that in the next version of this code and build on top of
this patch.
This way the existing exploiter (iscsi-initiator-utils) can use the parsing
code it already has to extract the data from the binary blob. Then in the
next version of the iscsi-initiator-utils (and for the kernel) I can post a
patch for supporting (and exporting in the kernel) individual sysfs attribute
files.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
