From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Tom Gall <tom.gall@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: android/android-4.4 build: 210 builds: 0 failed, 210 passed, 6 warnings (ASB-2017-10-5_4.4-o-release-513-gec888d46d899)
Date: Tue, 17 Oct 2017 16:36:59 +0200 [thread overview]
Message-ID: <20171017143659.GB10740@kroah.com> (raw)
In-Reply-To: <CAK8P3a082u7eoKfLDwWjcoy5WUYz=eUXuCMBQGW9WsgjAtqAGw@mail.gmail.com>
On Tue, Oct 17, 2017 at 10:51:22AM +0200, Arnd Bergmann wrote:
> On Tue, Oct 17, 2017 at 1:27 AM, kernelci.org bot <bot@kernelci.org> wrote:
> >
> >
> > Warnings summary:
> >
> > 1 net/wireless/nl80211.c:5096:1: warning: the frame size of 2064 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> > 1 net/wireless/nl80211.c:3859:1: warning: the frame size of 2168 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> > 1 net/wireless/nl80211.c:1728:1: warning: the frame size of 5640 bytes is larger than 2048 bytes [-Wframe-larger-than=]
>
> Hi Greg,
>
> I saw you backported my fix for this is to stable/linux-4.9.y, but I
> don't see it
> in 4.4.y. Can you add it here as well, or do you want help resolving a conflict?
>
> The upstream commit is b4391db42308 ("netlink: fix
> nla_put_{u8,u16,u32} for KASAN")
>
> > 1 drivers/platform/goldfish/goldfish_pipe_v2.c:340:1: warning: the frame size of 2736 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> > 1 drivers/platform/goldfish/goldfish_pipe_v2.c:340:1: warning: the frame size of 2720 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> > 1 drivers/platform/goldfish/goldfish_pipe_v2.c:340:1: warning: the frame size of 1368 bytes is larger than 1024 bytes [-Wframe-larger-than=]
>
> This is then the only remaining warning in 4.4. We've discussed it a few times
> before but not concluded on how to best fix it. The warning exists only in
> the android trees, mainline and stable don't have it.
If you can backport the fix, I'll take it. As it is, it doesn't apply
cleanly.
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-17 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59e5405c.9b88df0a.6da25.e5df@mx.google.com>
2017-10-17 8:51 ` Arnd Bergmann
2017-10-17 14:36 ` gregkh [this message]
2017-10-17 16:08 ` Arnd Bergmann
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=20171017143659.GB10740@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=anmar.oueja@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tom.gall@linaro.org \
/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
all inboxes | Powered by JetHome®