pt., 10 maj 2019 o 18:22 Anton Ivanov <anton.iva...@cambridgegreys.com> napisał(a): > > > On 10/05/2019 17:20, Bartosz Golaszewski wrote: > > pt., 10 maj 2019 o 11:16 Bartosz Golaszewski <b...@bgdev.pl> napisał(a): > >> śr., 8 maj 2019 o 09:13 Richard Weinberger <rich...@nod.at> napisał(a): > >>> ----- Ursprüngliche Mail ----- > >>>>> Can you please check? > >>>>> This patch is already queued in -next. So we need to decide whether to > >>>>> revert or fix it now. > >>>>> > >>>> I am looking at it. It passed tests in my case (I did the usual round). > >>> It works here too. That's why I never noticed. > >>> Yesterday I noticed just because I looked for something else in the > >>> kernel logs. > >>> > >>> Thanks, > >>> //richard > >> Hi, > >> > >> sorry for the late reply - I just came back from vacation. > >> > >> I see it here too, I'll check if I can find the culprit and fix it today. > >> > >> Bart > > Hi Richard, Anton, > > > > I'm not sure yet what this is caused by. It doesn't seem to break > > anything for me but since it's a new error message I guess it's best > > to revert this patch (others are good) and revisit it for v5.3. > > Can you send me your command line and .config so I can try to reproduce it. >
Sure, the command line is: ./linux rootfstype=hostfs rootflags=<path to a regular buildroot rootfs> rw mem=48M The config is the regular x86_64_defconfig from arch/um. Bart
