From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kyle Huey <me@kylehuey.com>,
open list <linux-kernel@vger.kernel.org>,
"Robert O'Callahan" <robert@ocallahan.org>
Subject: Re: [git pull] vfs.git regression fix Re: Regression related to ipc shmctl compat
Date: Tue, 26 Sep 2017 02:46:56 +0100 [thread overview]
Message-ID: <20170926014656.GY32076@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFxsRN02ZUPZF8txCemx7+bEWCkdKnrZpeJiyJe3r-Rn9w@mail.gmail.com>
On Mon, Sep 25, 2017 at 06:37:28PM -0700, Linus Torvalds wrote:
> And I think your recent compat cleanup work actually made it worse,
> showing new warnings (including the one that was a real bug)
Actually, they are not new - try make C=2 ipc/compat.o on v4.13 and you'll
see their previous locations.
> Patch to at least fix the address space warnings in ipc/ attached.
Which tree do you prefer it to go through? Direct to mainline, or vfs.git
#for-next?
next prev parent reply other threads:[~2017-09-26 1:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:18 Regression related to ipc shmctl compat Kyle Huey
2017-09-26 1:00 ` [git pull] vfs.git regression fix " Al Viro
2017-09-26 1:37 ` Linus Torvalds
2017-09-26 1:46 ` Al Viro [this message]
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=20170926014656.GY32076@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.