public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>, Michal Hocko <mhocko@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Rik van Riel <riel@redhat.com>,
	Larry Woodman <lwoodman@redhat.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Tony Luck <tony.luck@intel.com>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Helge Diller <deller@gmx.de>,
	James Hogan <james.hogan@imgtec.com>,
	Laura Abbott <labbott@redhat.com>, Willy Tarreau <w@1wt.eu>,
	Greg KH <greg@kroah.com>, stable <stable@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: larger stack guard gap, between vmas
Date: Sat, 24 Jun 2017 19:29:00 +0100	[thread overview]
Message-ID: <1498328940.2655.44.camel@decadent.org.uk> (raw)
In-Reply-To: <alpine.LSU.2.11.1706240115300.1232@eggly.anvils>

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

On Sat, 2017-06-24 at 02:11 -0700, Hugh Dickins wrote:
> On Thu, 22 Jun 2017, Hugh Dickins wrote:
> > On Thu, 22 Jun 2017, Ben Hutchings wrote:
> > 
> > > Here's my attempt at a backport to 3.2.  This is only tested on
> > > x86_64 and I think I should introduce local variables for
> > > vma_start_gap() in a few places.  I had to cherry-pick commit
> > > 09884964335e "mm: do not grow the stack vma just because of an overrun
> > > on preceding vma" before this one (which was a clean cherry-pick).
> > 
> > Both your speed and your stamina are much better than mine; and your
> > patch belies your Sturgeon's law signature.  I haven't got beyond the
> > architectures yet in my parallel attempt, and you do appear to be
> > doing everything right (but a local variable often welcome, yes).
> > 
> > I'm giving up for the night, will contine tomorrow.
> > The only discrepancy I notice so far is that I have
> > arch/alpha/kernel/osf_sys.c
> > arch/ia64/mm/hugetlbpage.c
> > arch/sparc/kernel/sys_sparc_32.c
> > in my list of changed files, but they're not in yours.
> 
> And here's my attempt at a backport to 3.2.89, at last.
> I know it builds and boots and runs on x86 64 and 32,
> but that's about all that I've tried.
> 
> If you diff against yours (I preferred not to send that diff,
> because of the couple of rejects in yours against 3.2.89),
> you'll find most of the difference is just noise from where
> I used a variable, but you had not yet done so in yours.

Thanks, this is much nicer.

> But there are those three missing files, and there are a few
> places where I have a little "if (prev) {" block at the head of
> the loop after find_vma_prev(): I think those loops start off
> wrongly without that.

I also failed to update prev.

[...]
> So please at least take a look through the diff from yours, I
> think you'll find a few things to bring in, but a lot to ignore.

I think I'll take most of yours, thanks.

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


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

      reply	other threads:[~2017-06-24 18:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LSU.2.11.1706190355140.2626@eggly.anvils>
2017-06-22 12:30 ` [PATCH] mm: larger stack guard gap, between vmas Ben Hutchings
2017-06-22 12:46   ` Willy Tarreau
2017-06-22 12:58     ` Ben Hutchings
2017-06-22 13:10       ` Willy Tarreau
2017-06-22 13:28         ` Willy Tarreau
2017-06-22 13:15       ` [vs-plain] " Levente Polyak
2017-06-22 13:59         ` Willy Tarreau
2017-06-22 14:14           ` Ben Hutchings
2017-06-22 14:34             ` Willy Tarreau
2017-06-23  3:10               ` Andy Lutomirski
2017-06-23  4:42                 ` Linus Torvalds
2017-06-22 21:23             ` Helge Deller
2017-06-23  4:35   ` Hugh Dickins
2017-06-24  9:11     ` Hugh Dickins
2017-06-24 18:29       ` Ben Hutchings [this message]

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=1498328940.2655.44.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=Jason@zx2c4.com \
    --cc=deller@gmx.de \
    --cc=greg@kroah.com \
    --cc=hughd@google.com \
    --cc=james.hogan@imgtec.com \
    --cc=jejb@parisc-linux.org \
    --cc=kirill@shutemov.name \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwoodman@redhat.com \
    --cc=mhocko@kernel.org \
    --cc=oleg@redhat.com \
    --cc=riel@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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