[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #17556: kernel: cutting mapped file area cause zeroing of second part
From:       "Haiku" <trac () haiku-os ! org>
Date:       2022-01-27 12:18:19
Message-ID: 055.dc7d65b7118f1c05395f458cc4af3ae5 () haiku-os ! org
[Download RAW message or body]

--===============4492278970909719499==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#17556: kernel: cutting mapped file area cause zeroing of second part
----------------------------+----------------------------
  Reporter:  X512           |      Owner:  nobody
      Type:  bug            |     Status:  new
  Priority:  normal         |  Milestone:  Unscheduled
 Component:  System/Kernel  |    Version:  R1/Development
Resolution:                 |   Keywords:
Blocked By:                 |   Blocking:
  Platform:  All            |
----------------------------+----------------------------
Description changed by X512:

Old description:

> This is hrev55664.
>
> Steps to reproduce:
> 1. Map file to team address space with `mmap`.
> 2. Allocate anonymous virtual memory at middle of mapped file memory from
> (1).
> 3. Second mapped file part after the end of anonimous memory will be
> zeroed.
>
> This problem cause Wine to not work properly.

New description:

 This is hrev55664.

 Steps to reproduce:
 1. Map file to team address space with `mmap`.
 2. Allocate anonymous virtual memory at middle of mapped file memory from
 (1).
 3. Second mapped file part after the end of anonymous memory will be
 zeroed.

 This problem cause Wine to not work properly.

--
-- =

Ticket URL: <https://dev.haiku-os.org/ticket/17556#comment:1>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
--===============4492278970909719499==--

[prev in list] [next in list] [prev in thread] [next in thread]