cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jacek Konieczny <jajcus@jajcus.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] DLM regression in 64-bit 3.7.x Kernel?
Date: Tue, 19 Feb 2013 11:55:14 +0100	[thread overview]
Message-ID: <20130219115514.6111ba2b@jajo.eggsoft> (raw)

Hi,

I have recently upgraded my development cluster from 3.6.x to 3.7.1
kernel and clvmd stopped working (all locking operation result in 'Invalid
argument'). I have traced the problem to this call:

write(8, "\6\0\0\0\0\0\0\0\1\0\0\0\1\1\0\0\5@\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\320\307\351\326\277\177\0\0\20\17\36\331\277\177\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\313\351\326\277\177\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0Hlk5NeaVF0qhDF20RBq61EZaIj5yyUJgWxxs4ntZedP34Rj3E2wadZfVwtOcvpKb", 184) = -1 EINVAL (Invalid argument)

Kernel sources show only a few conditions which can result in the EINVAL error
and the one introduced by the 'dlm: check the maximum size of a request from
user' patch seemed suspicious to me.

The commit: http://git.kernel.org/?p=linux/kernel/git/teigland/linux-dlm.git;a=commitdiff;h=2b75bc9121e54e22537207b47b71373bcb0be41c

Should a 64-bit kernel really refuse requests using the 64-bit
dlm_write_request struct when compiled with CONFIG_COMPAT on?

To verify my suspicions I have compiled the 3.7.9 with a little patch dropping 
the '(count > sizeof(struct dlm_write_request32) + DLM_RESNAME_MAXLEN)' check,
which solved the problem for me.

The patch will follow, though I am still not sure this is the solution.

Greets,
	Jacek



             reply	other threads:[~2013-02-19 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 10:55 Jacek Konieczny [this message]
2013-02-19 11:40 ` [Cluster-devel] [PATCH] dlm: Allow 64-bit request when CONFIG_COMPAT is on Jacek Konieczny
2013-02-25 16:11 ` [Cluster-devel] DLM regression in 64-bit 3.7.x Kernel? David Teigland

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=20130219115514.6111ba2b@jajo.eggsoft \
    --to=jajcus@jajcus.net \
    /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;
as well as URLs for NNTP newsgroup(s).