From: Greg KH <gregkh@linuxfoundation.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Harsh Shandilya <msfjarvis@gmail.com>,
Sasha Levin <Alexander.Levin@microsoft.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [GIT PULL] commits for Linux 3.18
Date: Mon, 9 Apr 2018 19:41:26 +0200 [thread overview]
Message-ID: <20180409174126.GB15599@kroah.com> (raw)
In-Reply-To: <20180409161446.GA23745@flashbox>
On Mon, Apr 09, 2018 at 09:14:46AM -0700, Nathan Chancellor wrote:
> On Mon, Apr 09, 2018 at 05:12:49PM +0200, Greg KH wrote:
> > On Thu, Apr 05, 2018 at 12:40:48AM -0700, Nathan Chancellor wrote:
> > > On Thu, Apr 05, 2018 at 12:32:55PM +0530, Harsh Shandilya wrote:
> > > >
> > > >
> > > > On 5 April 2018 11:54:28 AM IST, Sasha Levin <Alexander.Levin@microsoft.com> wrote:
> > > > >-----BEGIN PGP SIGNED MESSAGE-----
> > > > >Hash: SHA512
> > > > >
> > > > >Hi Greg,
> > > > >
> > > > >Pleae pull commits for Linux 3.18 .
> > > > >
> > > > >I've sent a review request for all commits over a week ago and all
> > > > >comments were addressed.
> > > > >
> > > > >
> > > > >Thanks,
> > > > >Sasha
> > > > >
> > > > >=====
> > > > >
> > > > >
> > > > >The following changes since commit
> > > > >89dad4ea47357950b8ba09886e02ff4fd0793f9e:
> > > > >
> > > > > Linux 3.18.99 (2018-03-11 16:12:20 +0100)
> > > > >
> > > > >are available in the Git repository at:
> > > > >
> > > > >git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
> > > > >tags/for-greg-3.18-04052018
> > > > >
> > > > >for you to fetch changes up to
> > > > >5ea952bd1f538212d63bbd34b42e2cc769074259:
> > > > >
> > > > >signal/arm: Document conflicts with SI_USER and SIGFPE (2018-04-05
> > > > >00:51:03 -0400)
> > > > >
> > > > >- ----------------------------------------------------------------
> > > > >for-greg-3.18-04052018
> > > > >
> > > > >- ----------------------------------------------------------------
> > > > >Jason A. Donenfeld (1):
> > > > > skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow
> > > > >
> > > > This patch introduces build warnings[1] with GCC 7.3.1 that were fixed upstream by commit 3f29770723fe498a5c5f57c3a31a996ebdde03e1 ("ipsec: check return value of skb_to_sgvec always").
> > > >
> > > > [1] https://del.dog/delexogeqi.coffeescript
> > > > --
> > > > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > >
> > > I have backported this commit and verified it fixes the warnings. This
> > > affects 3.18, 4.4, and 4.9. I can send them if/when these patches are
> > > added. No other warnings appear on arm64 and x86_64.
> >
> > Do you happen to have a pointer to these backports? I tried a simple
> > one for 4.9.y and it didn't apply :(
> >
> > thanks,
> >
> > greg k-h
>
> There was some refractoring of the arguments to skb_to_sgvec and
> skb_to_sgvec_nomark in addition to the lines around them between 4.9 and
> 4.12. It's even worse between 3.18 and 4.4. I have the patch files
> sitting right here if you want me to send them over.
Yes please!
next prev parent reply other threads:[~2018-04-09 17:41 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 6:24 [GIT PULL] commits for Linux 3.18 Sasha Levin
2018-04-05 7:02 ` Harsh Shandilya
2018-04-05 7:40 ` Nathan Chancellor
2018-04-09 0:26 ` Sasha Levin
2018-04-09 12:04 ` Greg KH
2018-04-09 15:12 ` Greg KH
2018-04-09 16:14 ` Nathan Chancellor
2018-04-09 17:41 ` Greg KH [this message]
2018-04-09 17:08 ` Harsh Shandilya
[not found] ` <43DEA09E-D11B-4563-929A-50612C9BF724@gmail.com>
2018-04-05 7:26 ` Harsh Shandilya
2018-04-10 13:15 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 3:26 Sasha Levin
2018-11-05 19:11 Sasha Levin
2018-10-22 9:14 Sasha Levin
2018-10-16 16:40 Sasha Levin
2018-10-12 14:36 Sasha Levin
2018-10-08 15:02 Sasha Levin
2018-10-02 0:58 Sasha Levin
2018-09-28 0:26 Sasha Levin
2018-09-24 1:01 Sasha Levin
2018-09-17 23:46 Sasha Levin
2018-09-14 18:41 Sasha Levin
2018-09-10 14:28 Sasha Levin
2018-08-25 15:10 Sasha Levin
2018-08-28 14:11 ` Greg KH
2018-08-10 0:23 Sasha Levin
2018-08-22 8:45 ` Greg KH
2018-07-28 1:46 Sasha Levin
2018-07-28 10:54 ` Greg KH
2018-06-21 2:38 Sasha Levin
2018-07-05 18:20 ` Greg KH
2018-06-07 1:07 Sasha Levin
2018-06-05 4:00 Sasha Levin
2018-06-05 6:42 ` Harsh Shandilya
2018-06-05 7:30 ` Sasha Levin
2018-06-05 9:09 ` Harsh Shandilya
2018-06-05 18:46 ` Sasha Levin
2018-06-05 18:54 ` Harsh Shandilya
2018-06-05 18:59 ` Sasha Levin
2018-06-05 19:49 ` Harsh Shandilya
2018-06-06 14:20 ` Sasha Levin
2018-06-06 20:55 ` Harsh Shandilya
2018-05-19 16:59 Sasha Levin
2018-05-19 19:18 ` Harsh Shandilya
2018-05-28 8:04 ` Greg KH
2018-05-28 8:18 ` Greg KH
2018-05-28 8:47 ` Harsh Shandilya
2018-05-28 9:02 ` Greg KH
2018-04-27 2:01 Sasha Levin
2018-05-02 20:49 ` Greg KH
2018-04-15 21:38 Sasha Levin
2018-04-24 17:05 ` Greg KH
2018-04-26 16:19 ` Sasha Levin
2018-04-26 18:40 ` Harsh Shandilya
2018-03-19 15:38 Sasha Levin
2018-03-22 14:17 ` Greg KH
2018-03-15 22:41 Sasha Levin
2018-03-19 13:37 ` Greg KH
2018-02-25 0:59 Sasha Levin
2018-02-28 15:17 ` Greg KH
2018-02-04 16:04 Sasha Levin
2018-02-23 11:02 ` Greg KH
2018-01-28 22:32 Sasha Levin
2017-12-20 15:37 alexander.levin
2017-12-22 8:41 ` Greg KH
2017-12-14 16:13 alexander.levin
2017-12-18 14:05 ` Greg KH
2017-12-12 0:59 alexander.levin
2017-12-14 20:38 ` Greg KH
2017-12-02 15:46 alexander.levin
2017-12-06 15:39 ` Greg KH
2017-12-06 16:23 ` alexander.levin
2017-12-06 16:31 ` Greg KH
2017-11-30 22:02 alexander.levin
2017-12-02 8:50 ` Greg KH
2017-12-02 15:46 ` alexander.levin
2017-11-30 22:02 alexander.levin
2017-12-02 8:50 ` Greg KH
2017-11-30 22:02 alexander.levin
2017-12-01 9:13 ` Greg KH
2017-12-01 15:26 ` alexander.levin
2017-12-02 8:51 ` Greg KH
2017-11-24 17:14 alexander.levin
2017-11-28 9:59 ` Greg KH
2017-11-19 0:51 alexander.levin
2017-11-19 11:17 ` Greg KH
2017-11-08 20:45 Levin, Alexander (Sasha Levin)
2017-11-09 17:23 ` Greg KH
2017-10-25 1:40 Levin, Alexander (Sasha Levin)
2017-11-06 11:25 ` Greg KH
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=20180409174126.GB15599@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=msfjarvis@gmail.com \
--cc=natechancellor@gmail.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.