From: "Köry Maincent" <kory.maincent@bootlin.com>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <olteanv@gmail.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v1 1/1] ethtool: fix clearing of WoL flags
Date: Thu, 19 Oct 2023 15:27:43 +0200 [thread overview]
Message-ID: <20231019152743.09b28ef4@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20231019105048.l64jp2nd46fxjewt@lion.mk-sys.cz>
On Thu, 19 Oct 2023 12:50:48 +0200
Michal Kubecek <mkubecek@suse.cz> wrote:
> On Thu, Oct 19, 2023 at 12:21:14PM +0200, Köry Maincent wrote:
> > On Thu, 19 Oct 2023 11:51:40 +0200 > Michal Kubecek <mkubecek@suse.cz>
> > wrote:
> > >
> > > The issue was indeed introduced by commit 108a36d07c01 ("ethtool: Fix
> > > mod state of verbose no_mask bitset"). The problem is that a "no mask"
> > > verbose bitset only contains bit attributes for bits to be set. This
> > > worked correctly before this commit because we were always updating
> > > a zero bitmap (since commit 6699170376ab ("ethtool: fix application of
> > > verbose no_mask bitset"), that is) so that the rest was left zero
> > > naturally. But now the 1->0 change (old_val is true, bit not present in
> > > netlink nest) no longer works.
> >
> > Doh I had not seen this issue! Thanks you for reporting it.
> > I will send the revert then and will update the fix for next merge-window.
>
> Something like the diff below (against current mainline) might do the
> trick but it's just an idea, not even build tested.
Seems a good idea without adding too much complexity to the code.
Will try that and send it in next merge window.
Köry
next prev parent reply other threads:[~2023-10-19 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 7:09 [PATCH net v1 1/1] ethtool: fix clearing of WoL flags Oleksij Rempel
2023-10-19 9:05 ` Michal Kubecek
2023-10-19 9:12 ` Oleksij Rempel
2023-10-19 9:51 ` Michal Kubecek
2023-10-19 10:21 ` Köry Maincent
2023-10-19 10:50 ` Michal Kubecek
2023-10-19 10:54 ` Michal Kubecek
2023-10-19 13:27 ` Köry Maincent [this message]
2023-10-19 16:20 ` Florian Fainelli
2023-10-19 16:45 ` Michal Kubecek
2023-10-19 17:34 ` Florian Fainelli
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=20231019152743.09b28ef4@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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