From: Kalle Valo <kvalo@codeaurora.org>
To: Greg KH <greg@kroah.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Kevin Cernekee <cernekee@chromium.org>,
franky.lin@broadcom.com, brcm80211-dev-list.pdl@broadcom.com,
linux-wireless@vger.kernel.org, mnissler@chromium.org
Subject: Re: [PATCH V2 1/3] brcmfmac: Avoid possible out-of-bounds read
Date: Wed, 13 Sep 2017 07:20:05 +0300 [thread overview]
Message-ID: <87ingngrgq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170912123341.GA19179@kroah.com> (Greg KH's message of "Tue, 12 Sep 2017 05:33:41 -0700")
Greg KH <greg@kroah.com> writes:
> On Tue, Sep 12, 2017 at 10:18:00AM +0200, Arend van Spriel wrote:
>> + Greg KH
>>
>> On 9/12/2017 10:05 AM, Kalle Valo wrote:
>> > Arend van Spriel <arend.vanspriel@broadcom.com> writes:
>> >
>> > > It is actually in the stable-kernel-rules documentation [1]:
>> > >
>> > > """
>> > > Also, some patches may have kernel version prerequisites. This can be
>> > > specified in the following format in the sign-off area:
>> > >
>> > > .. code-block:: none
>> > >
>> > > Cc: <stable@vger.kernel.org> # 3.3.x
>> > >
>> > > The tag has the meaning of:
>> > >
>> > > .. code-block:: none
>> > >
>> > > git cherry-pick <this commit>
>> > >
>> > > For each "-stable" tree starting with the specified version.
>> > > """
>> >
>> > Yeah, but it says "starting with" which I interpret as "starting with
>> > string '3.3'". For example the commit here would be applied to 3.3.1,
>> > 3.3.2 and 3.3.3 etc but _not_ to 3.4, 3.4.1, 3.5 or any later release.
>> >
>> > Of course I can be way off here, wouldn't be the first :)
>>
>> Dito. I interpret "each -stable tree" as each stable branch in the stable
>> repository. Would Greg know?
>
> "# 3.8+" and "# 3.8" mean the same thing to me, we would never backport
> something to only a very specific kernel version, and leave newer kernel
> versions to not have that fix. That would be crazy, and would break our
> "no regressions" rule (i.e. newer kernels should always work as good as
> older kernels.)
Indeed, that would be crazy. Didn't think it like that, thanks for the
clarification.
> Don't get hung up on the semantics here people, it's not all that
> complicated, and I do it all by hand anyway :)
Manually? Oh man, that has to be so hard. I cannot understand how you
can do it.
--
Kalle Valo
prev parent reply other threads:[~2017-09-13 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 19:30 [PATCH V2 1/3] brcmfmac: Avoid possible out-of-bounds read Kevin Cernekee
2017-09-09 19:30 ` [PATCH V2 2/3] brcmfmac: Delete redundant length check Kevin Cernekee
2017-09-09 19:30 ` [PATCH V2 3/3] brcmfmac: Add check for short event packets Kevin Cernekee
2017-09-12 7:45 ` [V2,3/3] " Kalle Valo
2017-09-10 18:50 ` [PATCH V2 1/3] brcmfmac: Avoid possible out-of-bounds read Arend van Spriel
2017-09-12 5:48 ` Kalle Valo
2017-09-12 7:36 ` Arend van Spriel
2017-09-12 7:47 ` Kalle Valo
2017-09-12 7:59 ` Arend van Spriel
2017-09-12 8:05 ` Kalle Valo
2017-09-12 8:18 ` Arend van Spriel
2017-09-12 12:33 ` Greg KH
2017-09-13 4:20 ` Kalle Valo [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=87ingngrgq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=cernekee@chromium.org \
--cc=franky.lin@broadcom.com \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mnissler@chromium.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.