From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Stefani Seibold <stefani@seibold.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Sean Young <sean@mess.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit
Date: Fri, 8 Dec 2017 12:07:51 -0200 [thread overview]
Message-ID: <20171208120751.5c3d3165@vento.lan> (raw)
In-Reply-To: <1512045250.2568.1.camel@seibold.net>
Em Thu, 30 Nov 2017 13:34:10 +0100
Stefani Seibold <stefani@seibold.net> 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 <sean@mess.org> 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 __is_kfifo_ptr() to fail, which is caught
> > > by kfifo_alloc(), which now returns EINVAL.
> > >
> > > So, ensure that __is_kfifo_ptr() compares to the right structure.
> > >
> > > Signed-off-by: Sean Young <sean@mess.org>
> > > Acked-by: Stefani Seibold <stefani@seibold.net>
> >
> > Hi Stefani/Andrew,
> >
> > As this patch is required for the LIRC rework, would be ok if I would
> > merge it via the media tree?
> >
>
> It is okay by me. But the question remains why this patch wasn't
> already merged?
>
> Andrew: Any objections against this patch?
I'm assuming that merging via media tree is ok for Andrew. So, I guess
I'll just go ahead and merge it via my tree.
Thanks,
Mauro
prev parent reply other threads:[~2017-12-08 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1507618840.git.sean@mess.org>
2017-10-10 7:18 ` [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit Sean Young
2017-10-10 7:59 ` Sean Young
2017-11-30 12:29 ` Mauro Carvalho Chehab
2017-11-30 12:34 ` Stefani Seibold
2017-12-08 14:07 ` Mauro Carvalho Chehab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171208120751.5c3d3165@vento.lan \
--to=mchehab@s-opensource.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sean@mess.org \
--cc=stefani@seibold.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox