<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/scsi/osd, branch v3.4.66</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/scsi/osd?h=v3.4.66</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/scsi/osd?h=v3.4.66'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-07-13T18:03:41Z</updated>
<entry>
<title>block: do not pass disk names as format strings</title>
<updated>2013-07-13T18:03:41Z</updated>
<author>
<name>Kees Cook</name>
<email>keescook@chromium.org</email>
</author>
<published>2013-07-03T22:01:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a8139b5b8b1355c4909d90afa58b055aabe1a272'/>
<id>urn:sha1:a8139b5b8b1355c4909d90afa58b055aabe1a272</id>
<content type='text'>
commit ffc8b30866879ed9ba62bd0a86fecdbd51cd3d19 upstream.

Disk names may contain arbitrary strings, so they must not be
interpreted as format strings.  It seems that only md allows arbitrary
strings to be used for disk names, but this could allow for a local
memory corruption from uid 0 into ring 0.

CVE-2013-2851

Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>[SCSI] osd_uld: Bump MAX_OSD_DEVICES from 64 to 1,048,576</title>
<updated>2012-02-25T14:25:09Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2012-01-25T19:42:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=41f8ad76362e7aefe3a03949c43e23102dae6e0b'/>
<id>urn:sha1:41f8ad76362e7aefe3a03949c43e23102dae6e0b</id>
<content type='text'>
It used to be that minors where 8 bit. But now they
are actually 20 bit. So the fix is simplicity itself.

I've tested with 300 devices and all user-mode utils
work just fine. I have also mechanically added 10,000
to the ida (so devices are /dev/osd10000, /dev/osd10001 ...)
and was able to mkfs an exofs filesystem and access osds
from user-mode.

All the open-osd user-mode code uses the same library
to access devices through their symbolic names in
/dev/osdX so I'd say it's pretty safe. (Well tested)

This patch is very important because some of the systems
that will be deploying the 3.2 pnfs-objects code are larger
than 64 OSDs and will stop to work properly when reaching
that number.

CC: Stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;JBottomley@Parallels.com&gt;
</content>
</entry>
<entry>
<title>scsi: Fix up files implicitly depending on module.h inclusion</title>
<updated>2011-10-31T23:31:24Z</updated>
<author>
<name>Paul Gortmaker</name>
<email>paul.gortmaker@windriver.com</email>
</author>
<published>2011-05-27T13:47:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=acf3368ffb75fc4a83726655d697e79646fe4eb3'/>
<id>urn:sha1:acf3368ffb75fc4a83726655d697e79646fe4eb3</id>
<content type='text'>
The module.h header was implicitly present everywhere, so files
with no explicit include of the module infrastructure would build
anyway.  We are now removing the implicit include, and so we need
to call out the module.h file that we need explicitly.

Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
</content>
</entry>
<entry>
<title>osd: Kconfig remove wrong FIXME</title>
<updated>2011-09-22T11:14:05Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2011-08-15T18:52:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a8f8c45082cb78489c5e6050c372ddac73ae439e'/>
<id>urn:sha1:a8f8c45082cb78489c5e6050c372ddac73ae439e</id>
<content type='text'>
The OSD protocol calls for all kind of security levels that use
CRYPTO_HMAC and SH1, but the current code only supports NO_SEC,
which does not use any of these.

Remove a wrong FIXME that calls for them. Thanks Maxin for
reporting on this.

Reported-by: "Maxin B. John" &lt;maxin.john@gmail.com&gt;
Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
</content>
</entry>
<entry>
<title>[SCSI] libosd: osd_req_read_sg, optimize the single entry case</title>
<updated>2011-01-24T18:06:31Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2011-01-23T15:53:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4977c82504f58d7579acabd21688183eaa8768fb'/>
<id>urn:sha1:4977c82504f58d7579acabd21688183eaa8768fb</id>
<content type='text'>
Since sg-read is a bidi operation, it is a gain to convert
a single sg entry into a regular read. Better do this in the
generic layer then force each caller to do so.

Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] osd: checking NULL instead of ERR_PTR()</title>
<updated>2010-12-09T15:24:13Z</updated>
<author>
<name>Dan Carpenter</name>
<email>error27@gmail.com</email>
</author>
<published>2010-11-12T04:31:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=057f02a38e67a944a2d0b89bb0111efb9dbe6e6e'/>
<id>urn:sha1:057f02a38e67a944a2d0b89bb0111efb9dbe6e6e</id>
<content type='text'>
bio_map_kern() returns ERR_PTRs on failure and never returns NULL.

[jejb: remove redundant unlikely spotted by Tobias Klauser]
Signed-off-by: Dan Carpenter &lt;error27@gmail.com&gt;
Acked-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libosd: write/read_sg_kern API</title>
<updated>2010-10-26T15:42:35Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2010-10-19T14:13:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6dd1d8a7953cdc203c6eb694ce8eafe2dcd3e9da'/>
<id>urn:sha1:6dd1d8a7953cdc203c6eb694ce8eafe2dcd3e9da</id>
<content type='text'>
This is a trivial addition to the SG API that can receive kernel
pointers. It is only used by the out-of-tree test module. So
it's immediate need is questionable. For maintenance ease it might
just get in, as it's very small.

John.
do you need this in the Kernel, or is it only for osd_ktest.ko?

Signed-off-by: John A. Chandy &lt;john.chandy@uconn.edu&gt;
Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libosd: Support for scatter gather write/read commands</title>
<updated>2010-10-26T15:42:34Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2010-10-19T12:22:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e96e72c45a1e78e9266dd70113b851395a440ef3'/>
<id>urn:sha1:e96e72c45a1e78e9266dd70113b851395a440ef3</id>
<content type='text'>
This patch adds the Scatter-Gather (sg) API to libosd.
Scatter-gather enables a write/read of multiple none-contiguous
areas of an object, in a single call. The extents may overlap
and/or be in any order.

The Scatter-Gather list is sent to the target in what is called
a "cdb continuation segment". This is yet another possible segment
in the osd-out-buffer. It is unlike all other segments in that it
sits before the actual "data" segment (which until now was always
first), and that it is signed by itself and not part of the data
buffer. This is because the cdb-continuation-segment is considered
a spill-over of the CDB data, and is therefor signed under
OSD_SEC_CAPKEY and higher.

TODO: A new osd_finalize_request_ex version should be supplied so
the @caps received on the network also contains a size parameter
and can be spilled over into the "cdb continuation segment".

Thanks to John Chandy &lt;john.chandy@uconn.edu&gt; for the original
code, and investigations. And the implementation of SG support
in the osd-target.

Original-coded-by: John Chandy &lt;john.chandy@uconn.edu&gt;
Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libosd: Free resources in reverse order of allocation</title>
<updated>2010-10-26T15:42:31Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2010-10-19T12:21:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c4df46c49d8677158c7fb070a08e0d386c80205f'/>
<id>urn:sha1:c4df46c49d8677158c7fb070a08e0d386c80205f</id>
<content type='text'>
At osd_end_request first free the request that might
point to pages, then free these pages. In reverse order
of allocation. For now it's just anal neatness. When we'll
use mempools It'll also pay in performance.

Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libosd: Fix bug in attr_page handling</title>
<updated>2010-10-26T15:42:30Z</updated>
<author>
<name>Boaz Harrosh</name>
<email>bharrosh@panasas.com</email>
</author>
<published>2010-10-19T12:20:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ec6a0a41b57feb54b3830918a8fb07147c2ee778'/>
<id>urn:sha1:ec6a0a41b57feb54b3830918a8fb07147c2ee778</id>
<content type='text'>
The _osd_req_finalize_attr_page was off by a mile, when trying to
append the enc_get_attr segment instead of the proper set_attr segment.

Also properly support when we don't have any attribute to set while
getting a full page. And when clearing an attribute by setting it's
size to zero.

Reported-by: John Chandy &lt;john.chandy@uconn.edu&gt;
Signed-off-by: Boaz Harrosh &lt;bharrosh@panasas.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
</feed>
