<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/block, branch v2.6.26</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.26</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.26'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2008-07-04T17:40:09Z</updated>
<entry>
<title>cciss: read config to obtain max outstanding commands per controller</title>
<updated>2008-07-04T17:40:09Z</updated>
<author>
<name>Mike Miller</name>
<email>mike.miller@hp.com</email>
</author>
<published>2008-07-04T17:00:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=491539982aa01fa71de93c2a06ac5d890d4cf1e2'/>
<id>urn:sha1:491539982aa01fa71de93c2a06ac5d890d4cf1e2</id>
<content type='text'>
This patch changes the way we determine the maximum number of outstanding
commands for each controller.

Most Smart Array controllers can support up to 1024 commands, the notable
exceptions are the E200 and E200i.

The next generation of controllers which were just added support a mode of
operation called Zero Memory Raid (ZMR).  In this mode they only support
64 outstanding commands.  In Full Function Raid (FFR) mode they support
1024.

We have been setting the queue depth by arbitrarily assigning some value
for each controller.  We needed a better way to set the queue depth to
avoid lots of annoying "fifo full" messages.  So we made the driver a
little smarter.  We now read the config table and subtract 4 from the
returned value.  The -4 is to allow some room for ioctl calls which are
not tracked the same way as io commands are tracked.

Please consider this for inclusion.

Signed-off-by: Mike Miller &lt;mike.miller@hp.com&gt;
Cc: Jens Axboe &lt;jens.axboe@oracle.com&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>cciss: fix regression that no device nodes are created if no logical drives are configured.</title>
<updated>2008-07-04T17:40:06Z</updated>
<author>
<name>Stephen M. Cameron</name>
<email>scameron@beardog.cca.cpqcorp.net</email>
</author>
<published>2008-07-04T16:59:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=77b96bd7e5ee0b44aed1b77fef5949bc19e8301f'/>
<id>urn:sha1:77b96bd7e5ee0b44aed1b77fef5949bc19e8301f</id>
<content type='text'>
Fix regression in cciss driver that if no logical drives are configured,
no device nodes at all get created.

Signed-off-by: Stephen M. Cameron &lt;scameron@beardog.cca.cpqcorp.net&gt;
Acked-by: Mike Miller &lt;mike.miller@hp.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>cciss: add new hardware support</title>
<updated>2008-06-13T01:05:40Z</updated>
<author>
<name>Mike Miller</name>
<email>mike.miller@hp.com</email>
</author>
<published>2008-06-12T22:21:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302'/>
<id>urn:sha1:24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302</id>
<content type='text'>
Add support for the next generation of HP Smart Array SAS/SATA
controllers.  Shipping date is late Fall 2008.

Bump the driver version to 3.6.20 to reflect the new hardware support from
patch 1 of this set.

Signed-off-by: Mike Miller &lt;mike.miller@hp.com&gt;
Cc: Jens Axboe &lt;jens.axboe@oracle.com&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Add 'rd' alias to new brd ramdisk driver</title>
<updated>2008-06-05T21:23:12Z</updated>
<author>
<name>Nick Piggin</name>
<email>npiggin@suse.de</email>
</author>
<published>2008-06-04T15:18:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=efedf51c866130945b5db755cb58670e60205d83'/>
<id>urn:sha1:efedf51c866130945b5db755cb58670e60205d83</id>
<content type='text'>
Alias brd to rd in the hope of helping legacy users. Suggested by Jan.

Signed-off-by: Nick Piggin &lt;npiggin@suse.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>virtio_blk: allow read-only disks</title>
<updated>2008-05-30T05:09:44Z</updated>
<author>
<name>Christian Borntraeger</name>
<email>borntraeger@de.ibm.com</email>
</author>
<published>2008-05-16T09:17:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3ef536095446552823fc488fec1c5451aab1260d'/>
<id>urn:sha1:3ef536095446552823fc488fec1c5451aab1260d</id>
<content type='text'>
Hello Rusty,

sometimes it is useful to share a disk (e.g. usr). To avoid file system
corruption, the disk should be mounted read-only in that case. This patch
adds a new feature flag, that allows the host to specify, if the disk should
be considered read-only.

Signed-off-by: Christian Borntraeger &lt;borntraeger@de.ibm.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>Fix crash in virtio_blk during modprobe ; rmmod ; modprobe</title>
<updated>2008-05-30T05:09:41Z</updated>
<author>
<name>Chris Lalancette</name>
<email>clalance@redhat.com</email>
</author>
<published>2008-05-30T20:09:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ac9d463afb1ca2434335351f3b7d9e4c8f8470e9'/>
<id>urn:sha1:ac9d463afb1ca2434335351f3b7d9e4c8f8470e9</id>
<content type='text'>
Fix a modprobe virtio_blk ; rmmod virtio_blk ; modprobe virtio_blk crash; this
was basically because we weren't doing "del_gendisk()" in the remove path.

Signed-off-by: Chris Lalancette &lt;clalance@redhat.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt; (moved del_gendisk up)
</content>
</entry>
<entry>
<title>brd: don't show ramdisks in /proc/partitions</title>
<updated>2008-05-24T16:56:11Z</updated>
<author>
<name>Marcin Krol</name>
<email>hawk@pld-linux.org</email>
</author>
<published>2008-05-23T20:04:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=53978d0a7a27eb036b9bf33c4caa06257a9dbed7'/>
<id>urn:sha1:53978d0a7a27eb036b9bf33c4caa06257a9dbed7</id>
<content type='text'>
In 2.6.25, ramdisk devices show up in /proc/partitions, which is a
behaviour change from the old rd.c.  Add GENHD_FL_SUPPRESS_PARTITION_INFO,
which was present in rd.c.

All kernels prior to 2.6.25 weren't displaying ramdisks in
/proc/partitions.  Since there are many userspace tools using information
from /proc/partitions some of them may now behave incorrectly (I didn't
tested any though).  For example before 2.6.25 /proc/partitions was empty
if no block devices like hard disks and such were detected by kernel.  Now
all 16 ramdisks are always visible there.  Some software may rely on such
information (I mean, on empty /proc/partitions).

There was quite similar situation back in 2004, and ramdisks were excluded
back from displaying.  Thats why I called this a regression (maybe a bit
unfortunate).  See this patch for info:
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3-rc2/2.6.3-rc2-mm1/broken-out/nbd-proc-partitions-fix.patch

I also think that someone somewhere (long time ago) excluded ramdisks from
/proc/partitions for good reasons.  It is possible that now such new
"feature" is harmless, but I think there are more chances that someone
will say "hey, /proc/partitions has changed, now my software doesn't work"
then "hey where did my new 2.6.25 feature go".  nbd devices are also
excluded, maybe for very same (unknown to me) reasons.

Signed-off-by: Marcin Krol &lt;hawk@pld-linux.org&gt;
Signed-off-by: Nick Piggin &lt;npiggin@suse.de&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] iSeries: Remove unused mail address</title>
<updated>2008-05-23T06:45:04Z</updated>
<author>
<name>Stephen Rothwell</name>
<email>sfr@canb.auug.org.au</email>
</author>
<published>2008-05-23T01:41:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8962cadbe7cbc4ed0fff94f56ebab505a10afd2e'/>
<id>urn:sha1:8962cadbe7cbc4ed0fff94f56ebab505a10afd2e</id>
<content type='text'>
I don't use my IBM email address normally and people can find me in
CREDITS.

Signed-off-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>m68k: Return -ENODEV if no device is found</title>
<updated>2008-05-18T20:28:50Z</updated>
<author>
<name>Geert Uytterhoeven</name>
<email>geert@linux-m68k.org</email>
</author>
<published>2008-05-18T18:47:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fd5b462f0b3ae641e39966d1c6cd0dd66100cda5'/>
<id>urn:sha1:fd5b462f0b3ae641e39966d1c6cd0dd66100cda5</id>
<content type='text'>
According to the tests in do_initcalls(), the proper error code in case no
device is found is -ENODEV, not -ENXIO or -EIO.

Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>block: avoid duplicate calls to get_part() in disk stat code</title>
<updated>2008-05-07T08:15:46Z</updated>
<author>
<name>Jens Axboe</name>
<email>jens.axboe@oracle.com</email>
</author>
<published>2008-05-07T08:15:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=28f13702f03e527fcb979747a882cf366c489c50'/>
<id>urn:sha1:28f13702f03e527fcb979747a882cf366c489c50</id>
<content type='text'>
get_part() is fairly expensive, as it O(N) loops over partitions
to find the right one. In lots of normal IO paths we end up looking
up the partition twice, to make matters even worse. Change the
stat add code to accept a passed in partition instead.

Signed-off-by: Jens Axboe &lt;jens.axboe@oracle.com&gt;
</content>
</entry>
</feed>
