Re: [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

Em Thu, 30 Nov 2017 13:34:10 +0100 Stefani Seibold escreveu: > On Thu, 2017-11-30 at 10:29 -0200, Mauro Carvalho Chehab wrote: > > Em Tue, 10 Oct 2017 09:59:42 +0200 > > Sean Young escreveu: > > > > > If you try to store u64 in a kfifo (or a struct with u64 members), > > > then the buf member

Re: [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

On Thu, 2017-11-30 at 10:29 -0200, Mauro Carvalho Chehab wrote: > Em Tue, 10 Oct 2017 09:59:42 +0200 > Sean Young escreveu: > > > If you try to store u64 in a kfifo (or a struct with u64 members), > > then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes > > padding due to alignment (note

Re: [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

Em Tue, 10 Oct 2017 09:59:42 +0200 Sean Young escreveu: > If you try to store u64 in a kfifo (or a struct with u64 members), > then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes > padding due to alignment (note that struct __kfifo is 20 bytes > on 32 bit). > > That in turn causes the _

[PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

If you try to store u64 in a kfifo (or a struct with u64 members), then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes padding due to alignment (note that struct __kfifo is 20 bytes on 32 bit). That in turn causes the __is_kfifo_ptr() to fail, which is caught by kfifo_alloc(), which now r

[PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

If you try to store u64 in a kfifo (or a struct with u64 members), then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes padding due to alignment (note that struct __kfifo is 20 bytes on 32 bit). That in turn causes the __is_kfifo_ptr() to fail, which is caught by kfifo_alloc(), which now r