<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/md, branch linux-2.6.22.y</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.22.y</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.22.y'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2007-11-05T17:56:07+00:00</updated>
<entry>
<title>dm snapshot: fix invalidation deadlock</title>
<updated>2007-11-05T17:56:07+00:00</updated>
<author>
<name>Milan Broz</name>
<email>mbroz@redhat.com</email>
</author>
<published>2007-07-12T16:28:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d91447ee784cf4954cea7e1e1018d1809d084f67'/>
<id>urn:sha1:d91447ee784cf4954cea7e1e1018d1809d084f67</id>
<content type='text'>
patch fcac03abd325e4f7a4cc8fe05fea2793b1c8eb75 in mainline

Process persistent exception store metadata IOs in a separate thread.

A snapshot may become invalid while inside generic_make_request().
A synchronous write is then needed to update the metadata while still
inside that function.  Since the introduction of
md-dm-reduce-stack-usage-with-stacked-block-devices.patch this has to
be performed by a separate thread to avoid deadlock.

Signed-off-by: Milan Broz &lt;mbroz@redhat.com&gt;
Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>dm: disable barriers</title>
<updated>2007-08-09T21:27:45+00:00</updated>
<author>
<name>Stefan Bader</name>
<email>shbader@de.ibm.com</email>
</author>
<published>2007-07-12T16:28:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b308574d183b5a91f52918bda2c0129b64527756'/>
<id>urn:sha1:b308574d183b5a91f52918bda2c0129b64527756</id>
<content type='text'>
This patch causes device-mapper to reject any barrier requests.  This is done
since most of the targets won't handle this correctly anyway.  So until the
situation improves it is better to reject these requests at the first place.
Since barrier requests won't get to the targets, the checks there can be
removed.

Signed-off-by: Stefan Bader &lt;shbader@de.ibm.com&gt;
Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>dm snapshot: permit invalid activation</title>
<updated>2007-08-09T21:27:44+00:00</updated>
<author>
<name>Milan Broz</name>
<email>mbroz@redhat.com</email>
</author>
<published>2007-07-12T16:28:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7afcfb0745af9fc90146c37565cd6998eaefc37f'/>
<id>urn:sha1:7afcfb0745af9fc90146c37565cd6998eaefc37f</id>
<content type='text'>
Allow invalid snapshots to be activated instead of failing.

This allows userspace to reinstate any given snapshot state - for
example after an unscheduled reboot - and clean up the invalid snapshot
at its leisure.

Signed-off-by: Milan Broz &lt;mbroz@redhat.com&gt;
Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>dm io: fix another panic on large request</title>
<updated>2007-08-09T21:27:42+00:00</updated>
<author>
<name>Jun'ichi Nomura</name>
<email>j-nomura@ce.jp.nec.com</email>
</author>
<published>2007-07-12T16:27:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=3bca2f557175e72b20f76d7489695f4c76ca0bf4'/>
<id>urn:sha1:3bca2f557175e72b20f76d7489695f4c76ca0bf4</id>
<content type='text'>
bio_alloc_bioset() will return NULL if 'num_vecs' is too large.
Use bio_get_nr_vecs() to get estimation of maximum number.

Signed-off-by: Junichi Nomura &lt;j-nomura@ce.jp.nec.com&gt;
Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>dm raid1: fix status</title>
<updated>2007-08-09T21:27:42+00:00</updated>
<author>
<name>Milan Broz</name>
<email>mbroz@redhat.com</email>
</author>
<published>2007-07-12T16:27:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=74ff092c258313747791da5d82054027167d1a79'/>
<id>urn:sha1:74ff092c258313747791da5d82054027167d1a79</id>
<content type='text'>
Fix mirror status line broken in dm-log-report-fault-status.patch:
  - space missing between two words
  - placeholder ("0") required for compatibility with a subsequent patch
  - incorrect offset parameter

Signed-off-by: Milan Broz &lt;mbroz@redhat.com&gt;
Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>dm io: fix panic on large request</title>
<updated>2007-08-09T21:27:37+00:00</updated>
<author>
<name>Milan Broz</name>
<email>mbroz@redhat.com</email>
</author>
<published>2007-07-21T11:37:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=2d68c23353ff6e72ca62a4d355f09332382d6796'/>
<id>urn:sha1:2d68c23353ff6e72ca62a4d355f09332382d6796</id>
<content type='text'>
Flush workqueue before releasing bioset and mopools in dm-crypt.  There can
be finished but not yet released request.

Call chain causing oops:
  run workqueue
    dec_pending
      bio_endio(...);
      	&lt;remove device request - remove mempool&gt;
      mempool_free(io, cc-&gt;io_pool);

This usually happens when cryptsetup create temporary
luks mapping in the beggining of crypt device activation.

When dm-core calls destructor crypt_dtr, no new request
are possible.

Signed-off-by: Milan Broz &lt;mbroz@redhat.com&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Cc: Patrick McHardy &lt;kaber@trash.net&gt;
Acked-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Cc: Christophe Saout &lt;christophe@saout.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>md: raid10: fix use-after-free of bio</title>
<updated>2007-08-09T21:27:36+00:00</updated>
<author>
<name>Maik Hampel</name>
<email>m.hampel@gmx.de</email>
</author>
<published>2007-07-31T07:37:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=058bfc1cc6700c210024dd9fd391ea8fbbb6c91a'/>
<id>urn:sha1:058bfc1cc6700c210024dd9fd391ea8fbbb6c91a</id>
<content type='text'>
In case of read errors raid10d tries to print a nice error message,
unfortunately using data from an already put bio.

Signed-off-by: Maik Hampel &lt;m.hampel@gmx.de&gt;
Acked-By: NeilBrown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>md: handle writes to broken raid10 arrays gracefully</title>
<updated>2007-08-09T21:27:36+00:00</updated>
<author>
<name>Arne Redlich</name>
<email>agr@powerkom-dd.de</email>
</author>
<published>2007-07-31T07:37:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=1eb34652551146be64def511d34a02178d9b00cd'/>
<id>urn:sha1:1eb34652551146be64def511d34a02178d9b00cd</id>
<content type='text'>
When writing to a broken array, raid10 currently happily emits empty bio
lists.  IOW, the master bio will never be completed, sending writers to
UNINTERRUPTIBLE_SLEEP forever.

Signed-off-by: Arne Redlich &lt;agr@powerkom-dd.de&gt;
Acked-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>md: fix bug in error handling during raid1 repair</title>
<updated>2007-06-16T20:16:15+00:00</updated>
<author>
<name>Mike Accetta</name>
<email>maccetta@laurelnetworks.com</email>
</author>
<published>2007-06-16T17:16:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=ed45666271f4fafa95b9d8ad44050e9a9bd2376e'/>
<id>urn:sha1:ed45666271f4fafa95b9d8ad44050e9a9bd2376e</id>
<content type='text'>
If raid1/repair (which reads all block and fixes any differences it finds)
hits a read error, it doesn't reset the bio for writing before writing
correct data back, so the read error isn't fixed, and the device probably
gets a zero-length write which it might complain about.

Signed-off-by: Neil Brown &lt;neilb@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>md: fix two raid10 bugs</title>
<updated>2007-06-16T20:16:15+00:00</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2007-06-16T17:16:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=af03b8e4e81c3789e597632268940edd11ffe870'/>
<id>urn:sha1:af03b8e4e81c3789e597632268940edd11ffe870</id>
<content type='text'>
1/ When resyncing a degraded raid10 which has more than 2 copies of each block,
  garbage can get synced on top of good data.

2/ We round the wrong way in part of the device size calculation, which
  can cause confusion.

Signed-off-by: Neil Brown &lt;neilb@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>
</feed>
