From: Stanislav Kinsburskiy <skinsbursky@virtuozzo.com>
To: raven@themaw.net
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@openvz.org, ldv@altlinux.org
Subject: [RFC PATCH 0/2] autofs: fix autofs_v5_packet dlivery in compat mode
Date: Fri, 01 Sep 2017 15:21:39 +0400 [thread overview]
Message-ID: <20170901110906.2669.1577.stgit@localhost.localdomain> (raw)
The problem is that in compat mode struct autofs_v5_packet has to have different size
(i.e. 4 bytes less).
This is RFC because:
1) This issue is hidden, because autofs pipe has O_DIRECT and the rest of the
epacket is truncated when read.
2) X86 arch doesn't have is_compat_task() helper
3) It's now clear, what to do if "pgrp" option is specified.
The following series implements...
---
Stanislav Kinsburskiy (2):
autofs: set compat flag on sbi when daemon uses 32bit addressation
autofs: sent 32-bit sized packet for 32-bit process
fs/autofs4/autofs_i.h | 3 +++
fs/autofs4/dev-ioctl.c | 3 +++
fs/autofs4/inode.c | 4 +++-
fs/autofs4/waitq.c | 5 +++++
4 files changed, 14 insertions(+), 1 deletion(-)
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next reply other threads:[~2017-09-01 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 11:21 Stanislav Kinsburskiy [this message]
2017-09-01 11:21 ` [RFC PATCH 1/2] autofs: set compat flag on sbi when daemon uses 32bit addressation Stanislav Kinsburskiy
2017-09-14 0:38 ` Ian Kent
2017-09-14 9:24 ` Stanislav Kinsburskiy
2017-09-14 11:29 ` Ian Kent
2017-09-14 11:39 ` Stanislav Kinsburskiy
2017-09-14 11:45 ` Ian Kent
2017-09-14 11:51 ` Stanislav Kinsburskiy
2017-09-01 11:21 ` [RFC PATCH 2/2] autofs: sent 32-bit sized packet for 32-bit process Stanislav Kinsburskiy
2017-09-14 0:32 ` [RFC PATCH 0/2] autofs: fix autofs_v5_packet dlivery in compat mode 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=20170901110906.2669.1577.stgit@localhost.localdomain \
--to=skinsbursky@virtuozzo.com \
--cc=autofs@vger.kernel.org \
--cc=devel@openvz.org \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.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).