public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	viro@zeniv.linux.org.uk, dhowells@redhat.com, raven@themaw.net
Subject: [PATCH] Force same size of struct autofs_v5_packet on x86 and x86_64
Date: Fri, 16 Sep 2011 12:06:38 +0200	[thread overview]
Message-ID: <1316167604.6545.84.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

autofs_v5_packet is 300 bytes on x86 and 304 bytes on x86_64.
This difference is wrong and leads to a hang in systemd when running
a x86 userspace on an x86_64 kernel.

Signed-off-by: Thomas Meyer <thomas@m3y3r>
---
 include/linux/auto_fs4.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/linux/auto_fs4.h b/include/linux/auto_fs4.h
index e02982f..4be222a 100644
--- a/include/linux/auto_fs4.h
+++ b/include/linux/auto_fs4.h
@@ -138,7 +138,7 @@ struct autofs_v5_packet {
 	__u32 tgid;
 	__u32 len;
 	char name[NAME_MAX+1];
-};
+} __attribute__ ((packed));
 
 typedef struct autofs_v5_packet autofs_packet_missing_indirect_t;
 typedef struct autofs_v5_packet autofs_packet_expire_indirect_t;
-- 
1.7.6.2


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-09-16 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 10:06 Thomas Meyer [this message]
2011-09-16 10:19 ` [PATCH] Force same size of struct autofs_v5_packet on x86 and x86_64 Al Viro
2011-09-16 10:38   ` Ian Kent
2011-09-18  8:01     ` Thomas Meyer
2011-09-19  3:52       ` Ian Kent
2011-09-19  6:10         ` Al Viro
2011-09-19  9:30           ` Thomas Meyer
2011-09-19 15:27             ` Al Viro
2011-09-20  3:07             ` Ian Kent

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=1316167604.6545.84.camel@localhost.localdomain \
    --to=thomas@m3y3r.de \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    --cc=viro@zeniv.linux.org.uk \
    /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