All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: "Özkan Göksu" <ozkangksu@gmail.com>, dm-devel@redhat.com
Subject: Re: device-mapper: ioctl: ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16)
Date: Wed, 19 Sep 2018 11:24:22 -0400	[thread overview]
Message-ID: <20180919152421.GA9101@redhat.com> (raw)
In-Reply-To: <09dfe022-a4a1-3fec-f998-ecfb0a477e44@redhat.com>

On Wed, Sep 19 2018 at  8:52am -0400,
Zdenek Kabelac <zkabelac@redhat.com> wrote:

> Dne 19.9.2018 v 12:35 Özkan Göksu napsal(a):
> >Hello.
> >I just upgraded my Kernel to: 4.14.70-1-lts | device-mapper
> >2.02.181-1 | multipath-tools 0.7.7-1
> >After that multipathd started to giving the log: // device-mapper:
> >ioctl: ioctl interface mismatch: kernel(4.37.0), user(4.39.0),
> >cmd(16)
> >It was working great on my ex kernel "4.14.30-1-lts" with |
> >device-mapper 2.02.177-5 | multipath-tools 0.7.6-1
> >Also I tried multipath git version but nothing change.
> >
> >I think the problem related to device-mapper and my device mapper
> >Build Date: 2018-08-01 19:05 UTC =
> >https://www.archlinux.org/packages/core/x86_64/device-mapper/
> >Do I need to compile device mapper git version or what should I do?
> >
> 
> Hi
> 
> Can you pastebin how is your package linked while being compiled (gcc log) and
> how is then used runtime  (ldd) ?
> 
> It seems the code was linked with different .so library then it's
> using in runtime.
> 
> libdm  is supposed to handle all kernel versions.

Right, we need to get to the bottom of this.  This is _not_ something
that users should hit.

  reply	other threads:[~2018-09-19 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 10:35 device-mapper: ioctl: ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16) Özkan Göksu
2018-09-19 11:48 ` Heinz Mauelshagen
2018-09-19 12:07   ` Özkan Göksu
2018-09-19 12:52 ` Zdenek Kabelac
2018-09-19 15:24   ` Mike Snitzer [this message]
2018-09-19 15:30   ` Özkan Göksu
2018-09-19 15:34     ` Mike Snitzer
2018-09-20 10:14     ` Zdenek Kabelac

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=20180919152421.GA9101@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ozkangksu@gmail.com \
    --cc=zkabelac@redhat.com \
    /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.