All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: Hannes Reinecke <hare@suse.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: SUSE multipath-tools patch resync
Date: Wed, 25 May 2011 13:14:39 +0200	[thread overview]
Message-ID: <1306322079.2290.25.camel@lapoo.opensvc.com> (raw)
In-Reply-To: <4DDCC72A.8000601@suse.de>

On mer., 2011-05-25 at 11:08 +0200, Hannes Reinecke wrote:
> On 05/25/2011 09:51 AM, Christophe Varoqui wrote:
> > On mer., 2011-05-18 at 17:03 +0200, Hannes Reinecke wrote:
> >> git.kernel.org:/pub/scm/linux/kernel/git/hare/multipath-tools.git
> >
> > I started the merge. I'll post comments along the reading. It seems
> > there won't be much : this patchset is clearly a must-have.
> >
> :-)
> 
> With some things so bloody obvious that I keep wondering if I'm the
> only one seeing these ...
> 
The merge is done. No change wrt your branch. Still not pushed to korg.
I struggle with a hwtable corruption with no /etc/multipath.conf ... can
you reproduce that ?

For example, iterating through the hwtable and printing ->product from
config.c:find_hwe() gives:

...
(StorEdge 3510|T4)
FC2502
RAIGE VOLUME
CSM200_R
LCSM100_[IEFS]
INF-01-00
FLEXLINE 380
\x01
\x01\x02hd\x03\x10
\x01dcssblk

The final spurious entries are clearly from the blacklist mem region. I
verified the hwtable is not corrupted after initialization. Corruption
thus occurs between hwtable init and path discovery.

I'll continue tracking it, but if you see something obvious ...

  reply	other threads:[~2011-05-25 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 15:03 SUSE multipath-tools patch resync Hannes Reinecke
2011-05-20  6:26 ` Christophe Varoqui
2011-05-25  7:51 ` Christophe Varoqui
2011-05-25  9:08   ` Hannes Reinecke
2011-05-25 11:14     ` Christophe Varoqui [this message]
2011-05-25 12:10       ` Christophe Varoqui
2011-05-25 12:22         ` Christophe Varoqui
2011-05-25 12:45           ` Hannes Reinecke
2011-05-25 21:29           ` Christophe Varoqui
2011-05-26  6:28             ` Hannes Reinecke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1306322079.2290.25.camel@lapoo.opensvc.com \
    --to=christophe.varoqui@gmail.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.