Fence for Malloc'ed Memory Characterization

Hi Where is the memory fence for allocations added? How much? Does it adjoin at the low and high end? If I malloc(1), what does the layout look like? Low Fence of N bytes 1 byte ??? Fence Filler High Fence of N bytes When is it checked? I didn't find the word fence in the

Re: [PATCH] add STM32H7 BSP variant to support STM32H7B3I-DK board

On 01/04/2022 22:15, Karel Gardas wrote: the patch set looks good, I will integrate it on Monday if there are no other comments over the weekend. Would be great! Thanks! Sorry, the repository access doesn't work for me after the server update. I will check it in as soon as it works again.

Re: [PATCH] imfs: Fix index underrun when extending empty file

Am 04.04.22 um 16:40 schrieb Joel Sherrill: On Mon, Apr 4, 2022, 9:28 AM Christian MAUDERER > wrote: Please note: I would like to apply this to the 5 branch too. I created a ticket for 5 here: https://devel.rtems.org/ticket/4638

Re: [PATCH] imfs: Fix index underrun when extending empty file

On Mon, Apr 4, 2022, 9:28 AM Christian MAUDERER < christian.maude...@embedded-brains.de> wrote: > Please note: I would like to apply this to the 5 branch too. I created a > ticket for 5 here: > >https://devel.rtems.org/ticket/4638 > > Note that both tickets (5 and 6) are clones of an old 4.11

Re: [PATCH] imfs: Fix index underrun when extending empty file

Please note: I would like to apply this to the 5 branch too. I created a ticket for 5 here: https://devel.rtems.org/ticket/4638 Note that both tickets (5 and 6) are clones of an old 4.11 ticket: https://devel.rtems.org/ticket/2353 I didn't plan to backport the patch to 4.11. I'll add a

[PATCH] imfs: Fix index underrun when extending empty file

Currently the following sequence causes a endless loop when extending an IMFS file: - Create a file with zero length and close it. - Make sure nearly no allocatable memory is left. - Open the file and write enough data into it that more than the remaining memory will be used. In that case when