mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo van Lil <inguin@gmx.de>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "dmurphy@ti.com" <dmurphy@ti.com>
Subject: Re: [PATCH] net: phy: dp83869: fix memory corruption when enabling fiber
Date: Tue, 1 Oct 2024 15:31:13 +0200	[thread overview]
Message-ID: <9e970294-912a-4bc4-8841-3515f789d582@gmx.de> (raw)
In-Reply-To: <c9baa43edbde4a6aab7ec32a25eec4dae7031443.camel@siemens.com>

On 10/1/24 12:40, Sverdlin, Alexander wrote:

>> diff --git a/drivers/net/phy/dp83869.c b/drivers/net/phy/dp83869.c
>> index d7aaefb5226b..9c5ac5d6a9fd 100644
>> --- a/drivers/net/phy/dp83869.c
>> +++ b/drivers/net/phy/dp83869.c
>> @@ -645,7 +645,7 @@ static int dp83869_configure_fiber(struct phy_device *phydev,
>>   		     phydev->supported);
>>
>>   	linkmode_set_bit(ETHTOOL_LINK_MODE_FIBRE_BIT, phydev->supported);
>> -	linkmode_set_bit(ADVERTISED_FIBRE, phydev->advertising);
>> +	linkmode_set_bit(ETHTOOL_LINK_MODE_FIBRE_BIT, phydev->advertising);
>
> Are you sure this linkmode_set_bit() is required at all?

You're right, it's probably not required. I just tracked a weird bug
down to this clear mistake and wanted to change as little as possible.

The logic of the function seems a bit odd to me: At the beginning,
advertising is ANDed with supported, and at the end it's ORed again.
Inside the function they are mostly manipulated together.

Couldn't that be replaced with a simple "phydev->advertising =
phydev->supported;" at the end?

Regards,
Ingo

  reply	other threads:[~2024-10-01 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  7:57 Ingo van Lil
2024-10-01 10:40 ` Sverdlin, Alexander
2024-10-01 13:31   ` Ingo van Lil [this message]
2024-10-01 13:45     ` Sverdlin, Alexander
2024-10-02 15:53       ` Andrew Lunn
2024-10-02 15:54 ` Andrew Lunn

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=9e970294-912a-4bc4-8841-3515f789d582@gmx.de \
    --to=inguin@gmx.de \
    --cc=alexander.sverdlin@siemens.com \
    --cc=dmurphy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®