On Sat, 7 May 2022 17:51:16 +0300 Vasily Averin <vvs@xxxxxxxxxx> wrote: > The same messages are generated for any other gfp_t argument in trace events. > As far as I understand it is not a bug per se, > but trace macros lacks __force attribute in 'gfp_t'-> 'unsigned long' casts. > The same thing happens with mode_t and with some other places using __print_flags() > for __bitwise marked types. I'm curious as to where the gfp_t to unsigned long is happening in the macros? -- Steve
