From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
"David S . Miller" <davem@davemloft.net>,
Stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2 for-4.9.y 0/5] net/sched: init failure fixes
Date: Thu, 13 Sep 2018 14:30:57 +0200 [thread overview]
Message-ID: <20180913123057.GH2268@kroah.com> (raw)
In-Reply-To: <1535007041-31605-1-git-send-email-amit.pundir@linaro.org>
On Thu, Aug 23, 2018 at 12:20:36PM +0530, Amit Pundir wrote:
> Hi Greg,
>
> Kindly consider/review following net/sched fixes for stable 4.9.y.
>
> This patchset is a follow-up of upstream fix
> 87b60cfacf9f ("net_sched: fix error recovery at qdisc creation")
> cherry-picked on stable 4.9.y.
>
> It fix null pointer dereferences due to uninitialized timer
> (qdisc watchdog) or double frees due to ->destroy cleaning up a
> second time. Here is the original submission
> https://www.mail-archive.com/netdev@vger.kernel.org/msg186003.html
>
> Cherry-picked and build tested on Linux 4.9.123 for ARCH=x86_64.
>
> These fixes are applicable for stable 4.4.y kernel as well, but
> one of the patches needed a minor rebasing, so I'm resending this
> series for 4.4.y in a separate thread to avoid any confusion.
Now applied for 4.4.y and 4.9.y, thanks.
greg k-h
prev parent reply other threads:[~2018-09-13 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 6:50 [PATCH v2 for-4.9.y 0/5] net/sched: init failure fixes Amit Pundir
2018-08-23 6:50 ` [PATCH v2 for-4.9.y 1/5] sch_htb: fix crash on init failure Amit Pundir
2018-08-23 6:50 ` [PATCH v2 for-4.9.y 2/5] sch_multiq: fix double free " Amit Pundir
2018-08-23 6:50 ` [PATCH v2 for-4.9.y 3/5] sch_hhf: fix null pointer dereference " Amit Pundir
2018-08-23 6:50 ` [PATCH v2 for-4.9.y 4/5] sch_netem: avoid null pointer deref " Amit Pundir
2018-08-23 6:50 ` [PATCH v2 for-4.9.y 5/5] sch_tbf: fix two null pointer dereferences " Amit Pundir
2018-09-13 12:30 ` 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=20180913123057.GH2268@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=davem@davemloft.net \
--cc=nikolay@cumulusnetworks.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.