From: Greg KH <greg@kroah.com>
To: Jon Maloy <jon.maloy@ericsson.com>
Cc: stable@vger.kernel.org, parthasarathy.bhuvaragan@ericsson.com,
ying.xue@windriver.com, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH stable 4.4] tipc: move premature initialization of stack variables
Date: Fri, 28 Apr 2017 09:45:46 +0200 [thread overview]
Message-ID: <20170428074546.GC30203@kroah.com> (raw)
In-Reply-To: <20170428074512.GB30203@kroah.com>
On Fri, Apr 28, 2017 at 09:45:12AM +0200, Greg KH wrote:
> On Thu, Apr 27, 2017 at 10:22:52PM +0200, Jon Maloy wrote:
> > From: Jon Paul Maloy <jon.maloy@ericsson.com>
> >
> > commit 681a55d71799b575f46fe94121728cf67460d1c3 upstream
> >
> > (Slightly modified to apply cleanly)
>
> Belongs below the --- line.
>
> >
> > In the function tipc_rcv() we initialize a couple of stack variables
> > from the message header before that same header has been validated.
> > In rare cases when the arriving header is non-linear, the validation
> > function itself may linearize the buffer by calling skb_may_pull(),
> > while the wrongly initialized stack fields are not updated accordingly.
> >
> > We fix this in this commit.
> >
> > Reported-by: Matthew Wong <mwong@sonusnet.com>
> > Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
> > Signed-off-by: David S. Miller <davem@davemloft.net>
> >
> > Conflicts:
> > net/tipc/node.c
>
> What are these lines for? Please don't do that, "Conflicts:" lines do
> not belong in the changelog as they don't make any sense, right?
Oh, and please fix this up and resend, I didn't take this patch.
greg k-h
prev parent reply other threads:[~2017-04-28 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 20:22 [PATCH stable 4.4] tipc: move premature initialization of stack variables Jon Maloy
2017-04-28 7:45 ` Greg KH
2017-04-28 7:45 ` Greg KH [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=20170428074546.GC30203@kroah.com \
--to=greg@kroah.com \
--cc=jon.maloy@ericsson.com \
--cc=parthasarathy.bhuvaragan@ericsson.com \
--cc=stable@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
/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.