From: Michael Schmitz <schmitzmic@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>,
linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org,
linux-mtd@lists.infradead.org, Greg Ungerer <gerg@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Christoph Hellwig <hch@infradead.org>,
wbx@openadk.org
Subject: Re: m68k 54418 fails to execute user space
Date: Sat, 29 Jun 2024 20:01:19 +1200 [thread overview]
Message-ID: <c7203054-2839-eb94-2be7-b27c0c3c7770@gmail.com> (raw)
In-Reply-To: <87msn4z15c.fsf@linux-m68k.org>
Hi Andreas,
Am 29.06.2024 um 18:57 schrieb Andreas Schwab:
> On Jun 29 2024, Michael Schmitz wrote:
>
>> No heap space allocated here. I would have expected that to cause an error
>> message from libc ...
>
> No, the heap starts at _end and there is still enough space before the
> next page boundary.
Right - not all that unusual then.
Thanks,
Michael
next prev parent reply other threads:[~2024-06-29 8:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:29 Jean-Michel Hautbois
2024-06-24 8:56 ` Jean-Michel Hautbois
2024-06-26 1:56 ` Michael Schmitz
2024-06-26 5:35 ` Jean-Michel Hautbois
2024-06-26 7:01 ` Jean-Michel Hautbois
2024-06-26 13:28 ` Jean-Michel Hautbois
2024-06-26 19:36 ` Michael Schmitz
2024-06-26 20:29 ` Jean-Michel Hautbois
2024-06-27 12:36 ` Jean-Michel Hautbois
2024-06-27 14:46 ` Greg Ungerer
2024-06-27 14:52 ` Jean-Michel Hautbois
2024-06-27 23:58 ` Michael Schmitz
2024-06-28 7:24 ` Jean-Michel Hautbois
2024-06-28 7:48 ` Michael Schmitz
2024-06-28 8:02 ` Jean-Michel Hautbois
2024-06-28 11:25 ` Jean-Michel Hautbois
2024-06-29 3:41 ` Michael Schmitz
2024-06-29 7:57 ` Jean-Michel Hautbois
[not found] ` <87msn4z15c.fsf@linux-m68k.org>
2024-06-29 8:01 ` Michael Schmitz [this message]
2024-06-30 22:35 ` Greg Ungerer
2024-07-01 5:47 ` Jean-Michel Hautbois
2024-07-01 8:01 ` Andreas Schwab
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=c7203054-2839-eb94-2be7-b27c0c3c7770@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=hch@infradead.org \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=schwab@linux-m68k.org \
--cc=wbx@openadk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox