Le 01/06/2020 à 03:23, Shoichi Yamaguchi a écrit :
Hi,
On Wed, May 27, 2020 at 8:47 PM Shoichi Yamaguchi wrote:
I modified virtio(4) not to allocate unused memory.
I guess it fixes the issue.
Could you check this?
I confirmed your closing the report on syzbot.
Hi,
On Wed, May 27, 2020 at 8:47 PM Shoichi Yamaguchi wrote:
>
> I modified virtio(4) not to allocate unused memory.
> I guess it fixes the issue.
>
> Could you check this?
I confirmed your closing the report on syzbot.
On 2020/06/01 9:36, Kamil Rytarowski wrote:
If you can find a use-case today in DDB for an exclusive allocator. I
have it ready and tested.
I intended to use it in ddb for one project, but that project is still
unfinished.
Good to know! I will ask you when I want it!
Thanks,
rin
On 01.06.2020 02:31, Rin Okuyama wrote:
> On 2020/06/01 9:23, Kamil Rytarowski wrote:
>> I wrote a tiny malloc (libc-style) implementation over a small static
>> storage (could be over stack or preallocated on the heap) without any
>> external dependencies.
>>
>> Would it be useful for you?
>
>
On 2020/06/01 9:23, Kamil Rytarowski wrote:
I wrote a tiny malloc (libc-style) implementation over a small static
storage (could be over stack or preallocated on the heap) without any
external dependencies.
Would it be useful for you?
At the moment, we need buffers only in db_show_callout(),
I wrote a tiny malloc (libc-style) implementation over a small static
storage (could be over stack or preallocated on the heap) without any
external dependencies.
Would it be useful for you?
On 01.06.2020 01:34, Rin Okuyama wrote:
> Module Name: src
> Committed By: rin
> Date: Sun May
"Rin Okuyama" writes:
> Module Name: src
> Committed By: rin
> Date: Sun May 31 08:33:48 UTC 2020
>
> Modified Files:
> src/sys/kern: kern_timeout.c
>
> Log Message:
> db_show_callout(): struct callout_cpu and cpu_info are too much for stack.
>
> XXX
> DDB can be running in the
> On May 31, 2020, at 1:33 AM, Rin Okuyama wrote:
>
> db_show_callout(): struct callout_cpu and cpu_info are too much for stack.
>
> XXX
> DDB can be running in the interrupt context, e.g., when activated from
> console. Therefore, use kmem_intr_alloc(9) instead of kmem_alloc(9).
>
> Frame
