From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Progyan Bhattacharya <bprogyan@gmail•com>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
narmstrong@baylibre•com, akpm@linux-foundation•org,
Arnd Bergmann <arnd@arndb•de>,
Daniel Golle <daniel@makrotopia•org>,
Joe Perches <joe@perches•com>
Subject: Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines
Date: Thu, 15 Feb 2018 16:09:22 +1100 [thread overview]
Message-ID: <20180215160922.39ea6c5d@canb.auug.org.au> (raw)
In-Reply-To: <CAGyWO1-356ncU=122yrqCoL96pCVfaqJwdFvkmqfot3fzVF6pg@mail.gmail.com>
Hi Progyan,
On Thu, 15 Feb 2018 10:04:18 +0530 Progyan Bhattacharya <bprogyan@gmail•com> wrote:
>
> I did some ground work and found this particular commit that causing the
> error.
>
> Commit Hash: d96977a8c2266792397ed9814bb84b5129a278ad
That hash does not appear in linux-next (or Linus' tree).
> Commit Body:
>
> kasan: rework Kconfig settings
>
> We get a lot of very large stack frames using gcc-7.0.1 with the default
> -fsanitize-address-use-after-scope --param asan-stack=1 options, which can
> easily cause an overflow of the kernel stack, e.g....
>
> Author(s):
>
> Signed-off-by: Arnd Bergmann <arnd@arndb•de>
> Acked-by: Andrey Ryabinin <aryabinin@virtuozzo•com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel•org>
> Cc: Andrey Ryabinin <aryabinin@virtuozzo•com>
> Cc: Alexander Potapenko <glider@google•com>
> Cc: Dmitry Vyukov <dvyukov@google•com>
> Cc: Andrey Konovalov <andreyknvl@google•com>
> Cc: <stable@vger•kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation•org>
> Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
That patch is in Linus' tree now (was in linux-next) but has SHA1 e7c52b84fb18
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2018-02-15 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 9:25 [PATCH] Build: Scripts/Makefile: Remove Repeated Lines Progyan Bhattacharya
2018-02-14 11:49 ` Stephen Rothwell
[not found] ` <CAGyWO1-9scERtpPw5CCwQcUbCU0SpcqpNq2eiBWRtwpRC-kB-A@mail.gmail.com>
2018-02-15 5:05 ` Stephen Rothwell
2018-02-15 5:24 ` Randy Dunlap
[not found] ` <CAGyWO1_tmrSB8WwyARGWXhYCz=SL-xqqU4d3Y0A1vqGWQ_8Trg@mail.gmail.com>
2018-02-15 17:52 ` Randy Dunlap
[not found] ` <CAGyWO1-356ncU=122yrqCoL96pCVfaqJwdFvkmqfot3fzVF6pg@mail.gmail.com>
2018-02-15 5:09 ` Stephen Rothwell [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=20180215160922.39ea6c5d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=bprogyan@gmail$(echo .)com \
--cc=daniel@makrotopia$(echo .)org \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=narmstrong@baylibre$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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