Re: [osv-dev] [PATCH] scheduler: Initialize _cpu field in detached_state struct

2019-08-08 Thread Geraldo Netto
Hey Waldek/Nadav/Friends, First of all, very nice to see all the work done :) We could setup clang analyzer [1] and american fuzzy lop [2] In the past I have ran it agains OSv but in the end, I didn't have the opportunity to work out the issues If I recall correctly, we had something like 400 case

Re: [osv-dev] [PATCH] scheduler: Initialize _cpu field in detached_state struct

2019-08-08 Thread Waldek Kozaczuk
I will next time. Got too excited and could not wait :-) Is there a GCC warning flag to detect these kind of bugs? Sent from my iPhone > On Aug 8, 2019, at 09:16, Nadav Har'El wrote: > > I wanted to apply this (thanks for finding and fixing this bug!), and saw > that you already did :-) > >

Re: [osv-dev] [PATCH] scheduler: Initialize _cpu field in detached_state struct

2019-08-08 Thread Nadav Har'El
I wanted to apply this (thanks for finding and fixing this bug!), and saw that you already did :-) If you commit your own patches which you had previously sent to the mailing llist, please do this with "git am -m" (or equivalently add the message-id line manually) so we get mail from the bot sayin

[osv-dev] [COMMIT osv master] scheduler: Initialize _cpu field in detached_state struct

2019-08-08 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Waldemar Kozaczuk Branch: master scheduler: Initialize _cpu field in detached_state struct The patch 97fe8aa3d2d8f2c938fcaa379c44ae5a80dfbf33 enhanced OSv to start using physical memory below 2MiB. The second MiB is part of the memory where OSv copies compres