From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: "Compostella,
Jeremy"
<jeremy.compostella-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] efibc: avoid stack overflow warning
Date: Sun, 1 May 2016 14:13:48 +0100 [thread overview]
Message-ID: <20160501131348.GS2839@codeblueprint.co.uk> (raw)
In-Reply-To: <2137916.p0oDBh93bk@wuerfel>
On Sun, 01 May, at 01:25:12AM, Arnd Bergmann wrote:
> On Saturday 30 April 2016 23:46:41 Matt Fleming wrote:
> >
> > > It's not something we'd have to worry about in practice, but it does
> > > make my patch incorrect. Should we come up with a different way to
> > > do it?
> >
> > Jeremy proposed a patch to dynamically allocate the memory, which I
> > think is the correct way to go given that our (reasonable) assumptions
> > about reboot notifier concurrency are not guaranteed,
> >
> > https://lkml.kernel.org/r/87h9eked24.fsf-e2kLcBBGnpIIbNWpFUBdLQzuBQEzu/OPQQ4Iyu8u01E@public.gmane.org
>
> Sure, that works. I considered doing it that way but it seemed more
> complicated. Please use that patch instead of mine.
Thanks Ard!
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Compostella, Jeremy" <jeremy.compostella@intel.com>,
Ingo Molnar <mingo@kernel.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efibc: avoid stack overflow warning
Date: Sun, 1 May 2016 14:13:48 +0100 [thread overview]
Message-ID: <20160501131348.GS2839@codeblueprint.co.uk> (raw)
In-Reply-To: <2137916.p0oDBh93bk@wuerfel>
On Sun, 01 May, at 01:25:12AM, Arnd Bergmann wrote:
> On Saturday 30 April 2016 23:46:41 Matt Fleming wrote:
> >
> > > It's not something we'd have to worry about in practice, but it does
> > > make my patch incorrect. Should we come up with a different way to
> > > do it?
> >
> > Jeremy proposed a patch to dynamically allocate the memory, which I
> > think is the correct way to go given that our (reasonable) assumptions
> > about reboot notifier concurrency are not guaranteed,
> >
> > https://lkml.kernel.org/r/87h9eked24.fsf@jcompost-MOBL1.tl.intel.com
>
> Sure, that works. I considered doing it that way but it seemed more
> complicated. Please use that patch instead of mine.
Thanks Ard!
next prev parent reply other threads:[~2016-05-01 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 17:48 [PATCH] efibc: avoid stack overflow warning Arnd Bergmann
2016-04-30 20:14 ` Matt Fleming
[not found] ` <20160430201449.GL2839-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-04-30 22:34 ` Arnd Bergmann
2016-04-30 22:34 ` Arnd Bergmann
2016-04-30 22:46 ` Matt Fleming
2016-04-30 22:46 ` Matt Fleming
[not found] ` <20160430224641.GQ2839-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-04-30 23:25 ` Arnd Bergmann
2016-04-30 23:25 ` Arnd Bergmann
2016-05-01 13:13 ` Matt Fleming [this message]
2016-05-01 13:13 ` Matt Fleming
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=20160501131348.GS2839@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=jeremy.compostella-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.