Re: [uml-devel] current_thread_info() returns invalid pointer in early UML boot code

[Vegard N. <veg...@gm...>]

On 12 June 2016 at 22:11, Richard Weinberger
<ric...@gm...> wrote:
>> I wonder why setup_env_path() ends up calling the kernel's snprintf(),
>> I thought that it would be using the glibc snprintf() at this point?
>
> That early you cannot use current() nor any other core kernel stuff
> since the kernel has not started so far.
> So, the current thread info struct points to garbage.

Yes, I know. I think setup_env_path() should call the libc snprintf
rather than the kernel one, can you explain how to do that properly?

Thanks,


Vegard