All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: Gidi Gal <gidi.gal.linux@gmail.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: "Invalid signature" issue on dev kernel launch
Date: Wed, 24 Mar 2021 10:59:45 -0400	[thread overview]
Message-ID: <108802.1616597985@turing-police> (raw)
In-Reply-To: <CAFSeFg-8hWzhw+Z6Fmquiq+v07s3boVZKb7LsYqv0wkrGhekZQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 478 bytes --]

On Wed, 24 Mar 2021 09:21:31 -0400, Aruna Hewapathirane said:

> > And all of that has to fit in 8K of stack. That's why we warn when things have
> > a large stack frame entry.

> I still don't understand why the 8K barrier ? Why can't we make it say 16K ?

The issue is that then you need 4 contiguous pages for fork() to succeed, which can
become a problem if memory gets fragmented.  The chances of being able to find
2 contiguous pages are *much* higher than 4.


[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-03-24 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 16:36 "Invalid signature" issue on dev kernel launch Gidi Gal
2021-03-23 21:08 ` Valdis Klētnieks
2021-03-24  2:25   ` Aruna Hewapathirane
2021-03-24  2:20 ` Aruna Hewapathirane
2021-03-24  2:36 ` Aruna Hewapathirane
2021-03-24  5:26   ` Valdis Klētnieks
2021-03-24 13:21     ` Aruna Hewapathirane
2021-03-24 14:59       ` Valdis Klētnieks [this message]
2021-03-24 12:58   ` Gidi Gal
2021-03-24 13:26     ` Aruna Hewapathirane
2021-03-24 15:17     ` Valdis Klētnieks
2021-03-24 13:12   ` Gidi Gal

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=108802.1616597985@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=aruna.hewapathirane@gmail.com \
    --cc=gidi.gal.linux@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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.