search for: kisskb

...ist of build error/warning regressions/improvements in > v5.7-rc1[1] compared to v5.6[2]. > > Summarized: > - build errors: +132/-3 > - build warnings: +257/-79 > > Happy fixing! ;-) > > Thanks to the linux-next team for providing the build service. > > [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8f3d9f354286745c751374f5f1fcafee6b3f3136/ (all 239 configs) > [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/7111951b8d4973bda27ff663f2cf18b663d15b48/ (all 239 configs) > > > *** ERRORS *** > > 132 error regressions: > + /kiss...

...ist of build error/warning regressions/improvements in > v5.7-rc1[1] compared to v5.6[2]. > > Summarized: > - build errors: +132/-3 > - build warnings: +257/-79 > > Happy fixing! ;-) > > Thanks to the linux-next team for providing the build service. > > [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8f3d9f354286745c751374f5f1fcafee6b3f3136/ (all 239 configs) > [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/7111951b8d4973bda27ff663f2cf18b663d15b48/ (all 239 configs) > > > *** ERRORS *** > > 132 error regressions: > + /kiss...

...vements in >> v5.7-rc1[1] compared to v5.6[2]. >> >> Summarized: >> - build errors: +132/-3 >> - build warnings: +257/-79 >> >> Happy fixing! ;-) >> >> Thanks to the linux-next team for providing the build service. >> >> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8f3d9f354286745c751374f5f1fcafee6b3f3136/ (all 239 configs) >> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/7111951b8d4973bda27ff663f2cf18b663d15b48/ (all 239 configs) >> >> >> *** ERRORS *** >> >> 132 error re...

...]. > >> > >> Summarized: > >> - build errors: +132/-3 > >> - build warnings: +257/-79 > >> > >> Happy fixing! ;-) > >> > >> Thanks to the linux-next team for providing the build service. > >> > >> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8f3d9f354286745c751374f5f1fcafee6b3f3136/ (all 239 configs) > >> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/7111951b8d4973bda27ff663f2cf18b663d15b48/ (all 239 configs) > >> > >> > >> *** ERRORS *** > >&...

On Mon, Jul 4, 2016 at 10:12 AM, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > JFYI, when comparing v4.7-rc6[1] to v4.7-rc5[3], the summaries are: > - build errors: +3/-2 + /home/kisskb/slave/src/drivers/vhost/vhost.c: error: call to '__compiletime_assert_844' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE: => 844:3 arm-randconfig > [1] http://kisskb.ellerman.id.au/kisskb/head/10562/ (260 out of 263 config...

On Mon, Jul 4, 2016 at 10:12 AM, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > JFYI, when comparing v4.7-rc6[1] to v4.7-rc5[3], the summaries are: > - build errors: +3/-2 + /home/kisskb/slave/src/drivers/vhost/vhost.c: error: call to '__compiletime_assert_844' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE: => 844:3 arm-randconfig > [1] http://kisskb.ellerman.id.au/kisskb/head/10562/ (260 out of 263 config...

...n Monday, July 4, 2016 10:21:45 AM CEST Geert Uytterhoeven wrote: > On Mon, Jul 4, 2016 at 10:12 AM, Geert Uytterhoeven > <geert at linux-m68k.org> wrote: > > JFYI, when comparing v4.7-rc6[1] to v4.7-rc5[3], the summaries are: > > - build errors: +3/-2 > > + /home/kisskb/slave/src/drivers/vhost/vhost.c: error: call to > '__compiletime_assert_844' declared with attribute error: BUILD_BUG_ON > failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE: => 844:3 > > arm-randconfig > > > [1] http://kisskb.ellerman.id.au/kisskb/head...

...ned int txqueue) > { > - __ei_tx_timeout(dev); > + __ei_tx_timeout(dev, txqueue); > } > EXPORT_SYMBOL(eip_tx_timeout); On Mon, Dec 9, 2019 at 6:37 AM <noreply at ellerman.id.au> wrote: > FAILED linux-next/m68k-defconfig/m68k Mon Dec 09, 16:34 > > http://kisskb.ellerman.id.au/kisskb/buildresult/14060060/ > > Commit: Add linux-next specific files for 20191209 > 6cf8298daad041cd15dc514d8a4f93ca3636c84e > Compiler: m68k-linux-gcc (GCC) 4.6.3 / GNU ld (GNU Binutils) 2.22 > > Possible errors > --------------- > > drivers/...

...f function 'vfree' [-Werror=implicit-function-declaration] > Both of those source files need to #include <linux/vmalloc.h>. > Full results trickling in here, not all the failures there are caused by > this patch, ie. some configs are broken in mainline: > > http://kisskb.ellerman.id.au/kisskb/head/13396/ > > cheers :) -- ~Randy

...f function 'vfree' [-Werror=implicit-function-declaration] > Both of those source files need to #include <linux/vmalloc.h>. > Full results trickling in here, not all the failures there are caused by > this patch, ie. some configs are broken in mainline: > > http://kisskb.ellerman.id.au/kisskb/head/13396/ > > cheers :) -- ~Randy

On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: > On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > As a result of backporting a bugfix, virtio_net started passing void * > > to page_address, assuming that it will get silently converted to struct > > page *. But this does not happen on architectures where page_address

On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: > On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > As a result of backporting a bugfix, virtio_net started passing void * > > to page_address, assuming that it will get silently converted to struct > > page *. But this does not happen on architectures where page_address

From: Randy Dunlap <rdunlap at infradead.org> Currently <linux/slab.h> #includes <linux/kmemleak.h> for no obvious reason. It looks like it's only a convenience, so remove kmemleak.h from slab.h and add <linux/kmemleak.h> to any users of kmemleak_* that don't already #include it. Also remove <linux/kmemleak.h> from source files that do not use it. This is

From: Randy Dunlap <rdunlap at infradead.org> Currently <linux/slab.h> #includes <linux/kmemleak.h> for no obvious reason. It looks like it's only a convenience, so remove kmemleak.h from slab.h and add <linux/kmemleak.h> to any users of kmemleak_* that don't already #include it. Also remove <linux/kmemleak.h> from source files that do not use it. This is

...mplicit-function-declaration] security/integrity/digsig.c:146:2: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration] Full results trickling in here, not all the failures there are caused by this patch, ie. some configs are broken in mainline: http://kisskb.ellerman.id.au/kisskb/head/13396/ cheers

...igsig.c:146:2: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration] > > Both of those source files need to #include <linux/vmalloc.h>. Yep, I added those and rebuilt. I don't see any more failures that look related to your patch. http://kisskb.ellerman.id.au/kisskb/head/13399/ I haven't gone through the defconfigs I have enabled for a while, so it's possible I have some missing but it's still a reasonable cross section. cheers

...anks for the clue! I was just investigating a similar failure in -next. >> >> Gr{oetje,eeting}s, >> >> Geert > > You don't mean linux-next? And not in virtio-net? I don't see page_address > being used on void * anywhere there. http://kisskb.ellerman.id.au/kisskb/buildresult/10469287/ I'm making {,set}page_address() static inline to fix this. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people,...

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout