From: Andrew Lunn <andrew@lunn.ch>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/6] ravb: remove custom .nway_reset from ethtool ops
Date: Thu, 24 May 2018 18:44:22 +0200 [thread overview]
Message-ID: <20180524164422.GI5128@lunn.ch> (raw)
In-Reply-To: <af16fdce-427e-c73a-b18b-d5f1c1d9d624@cogentembedded.com>
On Thu, May 24, 2018 at 07:18:28PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 05/24/2018 05:11 PM, Vladimir Zapolskiy wrote:
>
> >>> The change fixes a sleep in atomic context issue, which can be
> >>> always triggered by running 'ethtool -r' command, because
> >>> phy_start_aneg() protects phydev fields by a mutex.
>
> You don't say that *not* grabbing the spinlock is safe...
For it to be unsafe, i think that would mean phylib would need to call
back into the MAC driver? The only way that could happen is via the
adjust_link call. And that will deadlock, since it takes the same
lock.
Or am i/we missing something?
Andrew
next prev parent reply other threads:[~2018-05-24 16:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 11:11 [PATCH 0/6] ravb/sh_eth: fix sleep in atomic by reusing shared ethtool handlers Vladimir Zapolskiy
2018-05-24 11:11 ` [PATCH 1/6] ravb: remove custom .nway_reset from ethtool ops Vladimir Zapolskiy
2018-05-24 13:22 ` Andrew Lunn
2018-05-24 14:11 ` Vladimir Zapolskiy
2018-05-24 14:11 ` Vladimir Zapolskiy
2018-05-24 16:18 ` Sergei Shtylyov
2018-05-24 16:44 ` Andrew Lunn [this message]
2018-05-24 17:01 ` Sergei Shtylyov
2018-05-24 17:23 ` Andrew Lunn
2018-05-25 6:05 ` Vladimir Zapolskiy
2018-05-25 6:05 ` Vladimir Zapolskiy
2018-05-26 16:56 ` Sergei Shtylyov
2018-05-26 16:56 ` Sergei Shtylyov
2018-05-26 17:51 ` Sergei Shtylyov
2018-05-24 11:11 ` [PATCH 2/6] ravb: remove custom .get_link_ksettings " Vladimir Zapolskiy
2018-05-26 17:07 ` Sergei Shtylyov
2018-05-24 11:11 ` [PATCH 3/6] ravb: remove custom .set_link_ksettings " Vladimir Zapolskiy
2018-05-24 13:29 ` Andrew Lunn
2018-05-24 14:06 ` Vladimir Zapolskiy
2018-05-24 14:06 ` Vladimir Zapolskiy
2018-05-26 19:50 ` Sergei Shtylyov
2018-05-28 9:51 ` Vladimir Zapolskiy
2018-05-28 9:51 ` Vladimir Zapolskiy
2018-06-03 15:42 ` Sergei Shtylyov
2018-06-04 11:07 ` Vladimir Zapolskiy
2018-06-04 11:07 ` Vladimir Zapolskiy
2018-06-06 20:34 ` Sergei Shtylyov
2018-05-24 11:11 ` [PATCH 4/6] sh_eth: remove custom .nway_reset " Vladimir Zapolskiy
2018-05-24 13:30 ` Andrew Lunn
2018-05-26 18:46 ` Sergei Shtylyov
2018-05-26 19:22 ` Sergei Shtylyov
2018-05-24 11:14 ` [PATCH 5/6] sh_eth: remove custom .get_link_ksettings " Vladimir Zapolskiy
2018-05-24 11:14 ` [PATCH 6/6] sh_eth: remove custom .set_link_ksettings " Vladimir Zapolskiy
2018-05-24 13:31 ` [PATCH 5/6] sh_eth: remove custom .get_link_ksettings " Andrew Lunn
2018-05-24 16:40 ` [PATCH 0/6] ravb/sh_eth: fix sleep in atomic by reusing shared ethtool handlers Sergei Shtylyov
2018-05-24 17:24 ` Sergei Shtylyov
2018-05-25 6:25 ` Vladimir Zapolskiy
2018-05-25 6:25 ` Vladimir Zapolskiy
2018-05-26 17:31 ` Sergei Shtylyov
2018-05-25 8:11 ` Geert Uytterhoeven
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=20180524164422.GI5128@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vladimir_zapolskiy@mentor.com \
--cc=vz@mleia.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.