[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c062695f8d05a4c36a6d69f421b05208ac51fd2c.camel@sipsolutions.net>
Date: Mon, 28 Oct 2019 12:08:15 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Arnd Bergmann <arnd@...db.de>
Cc: David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
John Crispin <john@...ozen.org>
Subject: Re: pull-request: mac80211-next 2019-07-31
On Mon, 2019-10-28 at 11:53 +0100, Arnd Bergmann wrote:
>
> > Why do you say 32-bit btw, it should be *bigger* on 64-bit, but I didn't
> > see this ... hmm.
>
> That is correct. For historic reasons, both the total amount of stack space
> per thread and the warning limit on 64 bit are twice the amount that we
> have on 32-bit kernels, so even though the problem is more serious on
> 64-bit architectures, we do not see a warning about it because we remain
> well under the warning limit.
Hmm, but I have:
CONFIG_FRAME_WARN=1024
in my compilation?
Maybe I do in fact have merging of the storage space, and you don't? I
see another copy of it that shouldn't be merged ("bss_elems"), but ...
Hmm.
johannes
Powered by blists - more mailing lists