Re: kernel behaviour, was Re: dash behaviour

Hi Finn, On Tue, Apr 11, 2023 at 6:59 AM Finn Thain wrote: > On Tue, 11 Apr 2023, Michael Schmitz wrote: > > We don't know for definite that we deal with a suspect user space > > program - it might just be a change in a previously fine program that > > now exposes a subtle kernel bug (undetected

Re: kernel behaviour, was Re: dash behaviour

On Tue, 11 Apr 2023, Michael Schmitz wrote: > > > > I was able to find some command line options (init_on_alloc, > > init_on_free) and the related Kconfig symbols > > (CONFIG_INIT_ON_ALLOC_DEFAULT_ON, CONFIG_INIT_ON_FREE_DEFAULT_ON). > > Right - not sure how I managed to miss those. > > init_o

Re: kernel behaviour, was Re: dash behaviour

Hi Finn, Am 10.04.2023 um 21:39 schrieb Finn Thain: On Mon, 10 Apr 2023, Michael Schmitz wrote: So I guess this bug has more to do with timing and little to do with state, contrary to my guesswork above. And no doubt I will have to What may still vary is physical mapping - I remember you ha

kernel behaviour, was Re: dash behaviour

On Mon, 10 Apr 2023, Michael Schmitz wrote: > > > > So I guess this bug has more to do with timing and little to do with > > state, contrary to my guesswork above. And no doubt I will have to > > What may still vary is physical mapping - I remember you had used some > tool before to parse proc/