From: Hans Schultz <schultz.hans@gmail.com>
To: Ido Schimmel <idosch@idosch.org>, Vladimir Oltean <olteanv@gmail.com>
Cc: Petr Machata <petrm@nvidia.com>, Andrew Lunn <andrew@lunn.ch>,
Baowen Zheng <baowen.zheng@corigine.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Amit Cohen <amcohen@nvidia.com>,
netdev@vger.kernel.org, Hans Schultz <schultz.hans@gmail.com>,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Vivien Didelot <vivien.didelot@gmail.com>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
Po-Hsu Lin <po-hsu.lin@canonical.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>,
linux-kselftest@vger.kernel.org, Roopa Prabhu <roopa@nvidia.com>,
kuba@kernel.org, Stephen Suryaputra <ssuryaextr@gmail.com>,
Shuah Khan <shuah@kernel.org>,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next v3 4/5] net: dsa: mv88e6xxx: Add support for bridge port locked mode
Date: Mon, 21 Feb 2022 15:05:58 +0100 [thread overview]
Message-ID: <86h78sqpq1.fsf@gmail.com> (raw)
In-Reply-To: <YhIIJxxXP3JzD60/@shredder>
On sön, feb 20, 2022 at 11:21, Ido Schimmel <idosch@idosch.org> wrote:
> On Sat, Feb 19, 2022 at 12:00:34PM +0200, Vladimir Oltean wrote:
>> On Fri, Feb 18, 2022 at 04:51:47PM +0100, Hans Schultz wrote:
>> > diff --git a/drivers/net/dsa/mv88e6xxx/port.c b/drivers/net/dsa/mv88e6xxx/port.c
>> > index ab41619a809b..46b7381899a0 100644
>> > --- a/drivers/net/dsa/mv88e6xxx/port.c
>> > +++ b/drivers/net/dsa/mv88e6xxx/port.c
>> > @@ -1234,6 +1234,39 @@ int mv88e6xxx_port_set_mirror(struct mv88e6xxx_chip *chip, int port,
>> > return err;
>> > }
>> >
>> > +int mv88e6xxx_port_set_lock(struct mv88e6xxx_chip *chip, int port,
>> > + bool locked)
>> > +{
>> > + u16 reg;
>> > + int err;
>> > +
>> > + err = mv88e6xxx_port_read(chip, port, MV88E6XXX_PORT_CTL0, ®);
>> > + if (err)
>> > + return err;
>> > +
>> > + reg &= ~MV88E6XXX_PORT_CTL0_SA_FILT_MASK;
>> > + if (locked)
>> > + reg |= MV88E6XXX_PORT_CTL0_SA_FILT_DROP_ON_LOCK;
>> > +
>> > + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_CTL0, reg);
>> > + if (err)
>> > + return err;
>> > +
>> > + err = mv88e6xxx_port_read(chip, port, MV88E6XXX_PORT_ASSOC_VECTOR, ®);
>> > + if (err)
>> > + return err;
>> > +
>> > + reg &= ~MV88E6XXX_PORT_ASSOC_VECTOR_LOCKED_PORT;
>> > + if (locked)
>> > + reg |= MV88E6XXX_PORT_ASSOC_VECTOR_LOCKED_PORT;
>> > +
>> > + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_ASSOC_VECTOR, reg);
>>
>> return mv88e6xxx_port_write(...);
>
> Not familiar with mv88e6xxx, but shouldn't there be a rollback of
> previous operations? Specifically mv88e6xxx_port_write()
>
If a register write function fails, I don't think that it would make
sense to try and resolve the situation by additional register write
calls (rollback).
>>
>> > + if (err)
>> > + return err;
>> > +
>> > + return 0;
>> > +}
WARNING: multiple messages have this Message-ID (diff)
From: Hans Schultz <schultz.hans@gmail.com>
To: Ido Schimmel <idosch@idosch.org>, Vladimir Oltean <olteanv@gmail.com>
Cc: Hans Schultz <schultz.hans@gmail.com>,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>,
Shuah Khan <shuah@kernel.org>,
Stephen Suryaputra <ssuryaextr@gmail.com>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
Amit Cohen <amcohen@nvidia.com>,
Po-Hsu Lin <po-hsu.lin@canonical.com>,
Baowen Zheng <baowen.zheng@corigine.com>,
linux-kernel@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3 4/5] net: dsa: mv88e6xxx: Add support for bridge port locked mode
Date: Mon, 21 Feb 2022 15:05:58 +0100 [thread overview]
Message-ID: <86h78sqpq1.fsf@gmail.com> (raw)
In-Reply-To: <YhIIJxxXP3JzD60/@shredder>
On sön, feb 20, 2022 at 11:21, Ido Schimmel <idosch@idosch.org> wrote:
> On Sat, Feb 19, 2022 at 12:00:34PM +0200, Vladimir Oltean wrote:
>> On Fri, Feb 18, 2022 at 04:51:47PM +0100, Hans Schultz wrote:
>> > diff --git a/drivers/net/dsa/mv88e6xxx/port.c b/drivers/net/dsa/mv88e6xxx/port.c
>> > index ab41619a809b..46b7381899a0 100644
>> > --- a/drivers/net/dsa/mv88e6xxx/port.c
>> > +++ b/drivers/net/dsa/mv88e6xxx/port.c
>> > @@ -1234,6 +1234,39 @@ int mv88e6xxx_port_set_mirror(struct mv88e6xxx_chip *chip, int port,
>> > return err;
>> > }
>> >
>> > +int mv88e6xxx_port_set_lock(struct mv88e6xxx_chip *chip, int port,
>> > + bool locked)
>> > +{
>> > + u16 reg;
>> > + int err;
>> > +
>> > + err = mv88e6xxx_port_read(chip, port, MV88E6XXX_PORT_CTL0, ®);
>> > + if (err)
>> > + return err;
>> > +
>> > + reg &= ~MV88E6XXX_PORT_CTL0_SA_FILT_MASK;
>> > + if (locked)
>> > + reg |= MV88E6XXX_PORT_CTL0_SA_FILT_DROP_ON_LOCK;
>> > +
>> > + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_CTL0, reg);
>> > + if (err)
>> > + return err;
>> > +
>> > + err = mv88e6xxx_port_read(chip, port, MV88E6XXX_PORT_ASSOC_VECTOR, ®);
>> > + if (err)
>> > + return err;
>> > +
>> > + reg &= ~MV88E6XXX_PORT_ASSOC_VECTOR_LOCKED_PORT;
>> > + if (locked)
>> > + reg |= MV88E6XXX_PORT_ASSOC_VECTOR_LOCKED_PORT;
>> > +
>> > + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_ASSOC_VECTOR, reg);
>>
>> return mv88e6xxx_port_write(...);
>
> Not familiar with mv88e6xxx, but shouldn't there be a rollback of
> previous operations? Specifically mv88e6xxx_port_write()
>
If a register write function fails, I don't think that it would make
sense to try and resolve the situation by additional register write
calls (rollback).
>>
>> > + if (err)
>> > + return err;
>> > +
>> > + return 0;
>> > +}
next prev parent reply other threads:[~2022-02-21 14:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 15:51 [Bridge] [PATCH net-next v3 0/5] Add support for locked bridge ports (for 802.1X) Hans Schultz
2022-02-18 15:51 ` Hans Schultz
2022-02-18 15:51 ` [Bridge] [PATCH net-next v3 1/5] net: bridge: Add support for bridge port in locked mode Hans Schultz
2022-02-18 15:51 ` Hans Schultz
2022-02-19 9:46 ` [Bridge] " Nikolay Aleksandrov
2022-02-19 9:46 ` Nikolay Aleksandrov
2022-02-20 9:18 ` [Bridge] " Ido Schimmel
2022-02-20 9:18 ` Ido Schimmel
2022-02-18 15:51 ` [Bridge] [PATCH net-next v3 2/5] net: bridge: Add support for offloading of locked port flag Hans Schultz
2022-02-18 15:51 ` Hans Schultz
2022-02-19 9:47 ` [Bridge] " Nikolay Aleksandrov
2022-02-19 9:47 ` Nikolay Aleksandrov
2022-02-20 9:19 ` [Bridge] " Ido Schimmel
2022-02-20 9:19 ` Ido Schimmel
2022-02-18 15:51 ` [Bridge] [PATCH net-next v3 3/5] net: dsa: Add support for offloaded " Hans Schultz
2022-02-18 15:51 ` Hans Schultz
2022-02-19 9:56 ` [Bridge] " Vladimir Oltean
2022-02-19 9:56 ` Vladimir Oltean
2022-02-18 15:51 ` [Bridge] [PATCH net-next v3 4/5] net: dsa: mv88e6xxx: Add support for bridge port locked mode Hans Schultz
2022-02-18 15:51 ` Hans Schultz
2022-02-19 10:00 ` [Bridge] " Vladimir Oltean
2022-02-19 10:00 ` Vladimir Oltean
2022-02-20 9:21 ` [Bridge] " Ido Schimmel
2022-02-20 9:21 ` Ido Schimmel
2022-02-21 14:05 ` Hans Schultz [this message]
2022-02-21 14:05 ` Hans Schultz
2022-02-18 15:51 ` [Bridge] [PATCH net-next v3 5/5] selftests: forwarding: tests of locked port feature Hans Schultz
2022-02-18 15:51 ` Hans Schultz
2022-02-18 21:02 ` [Bridge] " Shuah Khan
2022-02-18 21:02 ` Shuah Khan
2022-02-19 9:48 ` [Bridge] " Nikolay Aleksandrov
2022-02-19 9:48 ` Nikolay Aleksandrov
2022-02-20 9:12 ` [Bridge] " Ido Schimmel
2022-02-20 9:12 ` Ido Schimmel
2022-02-21 9:20 ` [Bridge] " Hans Schultz
2022-02-21 9:20 ` Hans Schultz
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=86h78sqpq1.fsf@gmail.com \
--to=schultz.hans@gmail.com \
--cc=amcohen@nvidia.com \
--cc=andrew@lunn.ch \
--cc=baowen.zheng@corigine.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=petrm@nvidia.com \
--cc=po-hsu.lin@canonical.com \
--cc=roopa@nvidia.com \
--cc=shuah@kernel.org \
--cc=ssuryaextr@gmail.com \
--cc=vivien.didelot@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 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.