From: Greg KH <gregkh@linuxfoundation.org>
To: Mathias Tillman <master.homer@gmail.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
xiyou.wangcong@gmail.com, dsahern@gmail.com,
jeffy.chen@rock-chips.com, davem@davemloft.net,
khlebnikov@yandex-team.ru
Subject: Re: 4.4.103 linux kernel regression
Date: Sat, 23 Dec 2017 14:52:49 +0100 [thread overview]
Message-ID: <20171223135249.GA16617@kroah.com> (raw)
In-Reply-To: <CAKRBrgF3206o=0nwR63A2JqeRP82ZU9WZ3U9L=zR_dAjy3tL1g@mail.gmail.com>
adding stable@ and netdev@
On Sat, Dec 23, 2017 at 10:49:27AM +0000, Mathias Tillman wrote:
> Hi, I wanted to make you aware of a recent regression to the Linux kernel
> introduced with commit 2417da3f4d6bc4fc6c77f613f0e2264090892aa5:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/net/ipv6?h=linux-4.4.y&id=2417da3f4d6bc4fc6c77f613f0e2264090892aa5
Is this issue also present in Linus's tree?
> I have reported it here:
> https://bugzilla.kernel.org/show_bug.cgi?id=198189
Bugzilla doesn't work for networking bugs, nor stable stuff, just for a
few subsystems, sorry.
> Basically, that commit causes an endless loop if, for some reason, not all
> devices are unregistered in the rollback_registered_many function in
> net/dev.c
>
> Decided to contact you directly since I have yet to receive any reply on
> the bug report, and I wasn't entirely sure what the procedure was. Please
> do let me know if I have to change anything in the report.
I can revert it, but it would be good to verify if this is an issue in
the latest releases or not first.
thanks,
greg k-h
next parent reply other threads:[~2017-12-23 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKRBrgF3206o=0nwR63A2JqeRP82ZU9WZ3U9L=zR_dAjy3tL1g@mail.gmail.com>
2017-12-23 13:52 ` Greg KH [this message]
2017-12-23 16:36 ` 4.4.103 linux kernel regression Konstantin Khlebnikov
[not found] ` <CAKRBrgFT0_U=T4VhiSw69k8cMr-v+65gKbMpG4gh7=7ddNiFVg@mail.gmail.com>
2017-12-24 9:25 ` Konstantin Khlebnikov
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=20171223135249.GA16617@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jeffy.chen@rock-chips.com \
--cc=khlebnikov@yandex-team.ru \
--cc=master.homer@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).