From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: ramesh.shanmugasundaram@bp.renesas.com,
"linux-stable 3 . 16+" <stable@vger.kernel.org>
Subject: Re: [RFC] [PATCH] can: fix handling of unmodifiable configuration options
Date: Tue, 8 Mar 2016 19:22:20 +0100 [thread overview]
Message-ID: <56DF185C.7060300@hartkopp.net> (raw)
In-Reply-To: <1457457221-25068-1-git-send-email-socketcan@hartkopp.net>
On 03/08/2016 06:13 PM, Oliver Hartkopp wrote:
> As described in 'can: m_can: tag current CAN FD controllers as non-ISO'
> (6cfda7fbebe) it is possible to define fixed configuration options by
> setting the according bit in 'ctrlmode' and clear it in 'ctrlmode_supported'.
> This leads to the incovenience that the fixed configuration can not be passed
> by netlink (ip tool) even when it has the correct value (e.g. non-ISO, FD).
>
> This patch fixes that issue and allows fixed set bit values to be set again
> which does not change the unmodifiable content.
>
> Additionally it fixes the inconsitency that was prohibiting the support of
> 'CANFD-only' controller drivers.
>
> Reported-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> Cc: linux-stable <stable@vger.kernel.org> 3.16+
> ---
> drivers/net/can/dev.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c
> index 141c2a4..b084cfd 100644
> --- a/drivers/net/can/dev.c
> +++ b/drivers/net/can/dev.c
> @@ -696,11 +696,18 @@ int can_change_mtu(struct net_device *dev, int new_mtu)
> /* allow change of MTU according to the CANFD ability of the device */
> switch (new_mtu) {
> case CAN_MTU:
> + /* take care of 'CANFD-only' controllers */
> + if (!(priv->ctrlmode_supported & CAN_CTRLMODE_FD) &&
> + (priv->ctrlmode & CAN_CTRLMODE_FD))
> + return -EINVAL;
> +
> priv->ctrlmode &= ~CAN_CTRLMODE_FD;
> break;
>
> case CANFD_MTU:
> - if (!(priv->ctrlmode_supported & CAN_CTRLMODE_FD))
> + /* check for CANFD capability */
> + if (!(priv->ctrlmode_supported & CAN_CTRLMODE_FD) &&
> + !(priv->ctrlmode & CAN_CTRLMODE_FD))
> return -EINVAL;
>
> priv->ctrlmode |= CAN_CTRLMODE_FD;
> @@ -819,10 +826,13 @@ static int can_changelink(struct net_device *dev,
> return -EBUSY;
> cm = nla_data(data[IFLA_CAN_CTRLMODE]);
>
> - /* check whether changed bits are allowed to be modified */
> - if (cm->mask & ~priv->ctrlmode_supported)
> + /* check whether provided bits are allowed to be passed */
> + if (cm->mask & ~(priv->ctrlmode_supported | priv->ctrlmode))
> return -EOPNOTSUPP;
>
> + /* reduce to bits that are allowed to be modified */
> + cm->mask &= priv->ctrlmode_supported;
> +
I just realized that I'm updating a provided netlink attribute here.
Does anyone know, whether this is feasible OR if I need to spend an extra
variable to perform the '&=' operation?
Are netlink attributes to be treated as constants?
Thanks,
Oliver
> /* clear bits to be modified and copy the flag values */
> priv->ctrlmode &= ~cm->mask;
> priv->ctrlmode |= (cm->flags & cm->mask);
>
next prev parent reply other threads:[~2016-03-08 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 17:13 [RFC] [PATCH] can: fix handling of unmodifiable configuration options Oliver Hartkopp
2016-03-08 18:22 ` Oliver Hartkopp [this message]
2016-03-09 9:27 ` Ramesh Shanmugasundaram
2016-03-09 14:28 ` Oliver Hartkopp
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=56DF185C.7060300@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).