From: Al Viro <viro@ZenIV.linux.org.uk>
To: Kyle Huey <me@kylehuey.com>
Cc: open list <linux-kernel@vger.kernel.org>,
"Robert O'Callahan" <robert@ocallahan.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [git pull] vfs.git regression fix Re: Regression related to ipc shmctl compat
Date: Tue, 26 Sep 2017 02:00:36 +0100 [thread overview]
Message-ID: <20170926010036.GX32076@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAP045Ao2ciNysbNzfPOYaV_hyTCkgjo8KXnrtXHjYn3edPHeQA@mail.gmail.com>
On Mon, Sep 25, 2017 at 03:18:29PM -0700, Kyle Huey wrote:
> Beginning with 553f770ef71b, the following program fails when compiled
> for 32 bit and executed on a 64 bit kernel and succeeds when compiled
> for and executed on a 64 bit. It continues to fail even after
> 58aff0af7573. When compiled as 32 bit, an shmctl call fails with
> EBADR (see the XXX comment).
Egads...
static int put_compat_shm_info(struct shm_info *ip,
struct compat_shm_info __user *uip)
{
struct compat_shm_info info;
memset(&info, 0, sizeof(info));
info.used_ids = ip->used_ids;
info.shm_tot = ip->shm_tot;
info.shm_rss = ip->shm_rss;
info.shm_swp = ip->shm_swp;
info.swap_attempts = ip->swap_attempts;
info.swap_successes = ip->swap_successes;
return copy_to_user(up, &info, sizeof(info));
^^
This.
I really wish gcc warned about conversions from pointer to function into
void *...
Linus, could you pull that?
The following changes since commit 58aff0af757356065f33290d96a9cd46dfbcae88:
ipc/shm: Fix order of parameters when calling copy_compat_shmid_to_user (2017-09-20 23:27:48 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
for you to fetch changes up to b776e4b1a990045a7c70798f1f353c3160c26594:
fix a typo in put_compat_shm_info() (2017-09-25 20:41:46 -0400)
----------------------------------------------------------------
Al Viro (1):
fix a typo in put_compat_shm_info()
ipc/shm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next prev parent reply other threads:[~2017-09-26 1:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:18 Kyle Huey
2017-09-26 1:00 ` Al Viro [this message]
2017-09-26 1:37 ` [git pull] vfs.git regression fix " Linus Torvalds
2017-09-26 1:46 ` Al Viro
2017-09-26 2:00 ` Al Viro
2017-09-26 2:03 ` Linus Torvalds
2017-09-26 2:07 ` Linus Torvalds
2017-09-26 3:01 ` Al Viro
2017-09-26 19:45 ` Luc Van Oostenryck
2017-09-26 2:02 ` Linus Torvalds
2017-10-11 17:03 ` Al Viro
2017-10-11 17:06 ` Al Viro
2017-10-11 17:31 ` Linus Torvalds
2017-09-26 6:42 ` Christoph Hellwig
2017-09-28 6:13 ` Script to do smart sparse diffs (was Re: [git pull] vfs.git regression fix Re: Regression related to ipc shmctl compat) Michael Ellerman
2017-10-15 6:58 ` [git pull] vfs.git regression fix Re: Regression related to ipc shmctl compat Pavel Machek
2017-10-16 11:41 ` Linus Torvalds
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=20170926010036.GX32076@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=robert@ocallahan.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®