Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Bug in latest 8.4-git
Date: Wed, 8 Oct 2014 11:37:57 +0200	[thread overview]
Message-ID: <20141008093757.GF23433@soda.linbit> (raw)
In-Reply-To: <5432C17B.4050502@novg.net>

On Mon, Oct 06, 2014 at 08:21:15PM +0400, Igor Novgorodov wrote:
> I didn't found any bugtracker for DRBD project, so i reported the bug here.

Right thing to do. Thank you.

> ENOIOCTLCMD is returned in several places in net/socket.c and
> net/ipv4/tcp.c,
> it seems to have something to do with 32-bit code emulation on
> 64-bit kernel:
> 
> #ifdef CONFIG_COMPAT
> static int inet_compat_ioctl(struct socket *sock, unsigned int cmd,
> unsigned long arg)
> {
>          struct sock *sk = sock->sk;
>          int err = -ENOIOCTLCMD;
> 
>          if (sk->sk_prot->compat_ioctl)
>                  err = sk->sk_prot->compat_ioctl(sk, cmd, arg);
> 
>          return err;
> }
> #endif
> 
> CONFIG_COMPAT is only defined if 32-bit emulation is enabled in kernel.
> 
> I've just rebuilt kernel with CONFIG_X86_X32 and drbd-8.4-git
> started to work fine,
> so the problem is there, somewhere in 64/32 compatibility layer :)

Uh?
That is ... unexpected.

->listen() should do any ioctls, though?
and there is just kernel code talking to kernel code,
so why would CONFIG_X86_X32 matter at all?

Can you double check, please:
Is that reproducible, i.e., if you swich that CONFIG off again,
the error comes back?

(does not reproduce here... yet)

	Lars


  reply	other threads:[~2014-10-08  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 19:33 [Drbd-dev] Bug in latest 8.4-git Igor Novgorodov
2014-10-06 15:34 ` Lars Ellenberg
2014-10-06 16:21   ` Igor Novgorodov
2014-10-08  9:37     ` Lars Ellenberg [this message]
2014-10-08 10:31       ` Igor Novgorodov

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=20141008093757.GF23433@soda.linbit \
    --to=lars.ellenberg@linbit.com \
    --cc=drbd-dev@lists.linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox