From: Serge Semin <fancer.lancer@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: g@lunn.ch, Vicente Bergas <vicencb@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: net: phy: realtek: regression, kernel null pointer dereference
Date: Mon, 13 May 2019 16:01:33 +0300 [thread overview]
Message-ID: <20190513130131.jiommbisqvydmzgw@mobilestation> (raw)
In-Reply-To: <20190513125103.GC28969@lunn.ch>
On Mon, May 13, 2019 at 02:51:03PM +0200, Andrew Lunn wrote:
> > Ahh, I see. Then using lock-less version of the access methods must fix the
> > problem. You could try something like this:
>
> Kunihiko Hayash is way ahead of you.
>
> Andrew
I wouldn't say that five hours is "way ahead". But if something fixes a bug in
a patch it would be good to be have the original author being Cc'ed.
Vincente, here is a link to the patch, that fixes the problem.
https://lkml.org/lkml/2019/5/13/43
-Segey
next prev parent reply other threads:[~2019-05-13 13:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 15:05 net: phy: realtek: regression, kernel null pointer dereference Vicente Bergas
2019-05-10 20:28 ` Heiner Kallweit
2019-05-10 21:18 ` Vicente Bergas
2019-05-11 14:46 ` Vicente Bergas
2019-05-11 14:56 ` Heiner Kallweit
2019-05-11 15:06 ` Vicente Bergas
2019-05-13 10:29 ` Serge Semin
2019-05-13 10:51 ` Serge Semin
2019-05-13 12:19 ` Vicente Bergas
2019-05-13 12:42 ` Serge Semin
2019-05-13 12:51 ` Andrew Lunn
2019-05-13 13:01 ` Serge Semin [this message]
2019-05-13 13:33 ` Vicente Bergas
2019-05-13 7:29 ` Serge Semin
2019-05-11 15:08 ` Andrew Lunn
2019-05-11 15:16 ` Vicente Bergas
2019-05-11 15:25 ` Andrew Lunn
2019-05-10 21:04 ` Russell King - ARM Linux admin
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=20190513130131.jiommbisqvydmzgw@mobilestation \
--to=fancer.lancer@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=g@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=vicencb@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