From: Oliver Hartkopp <firstname.lastname@example.org>
To: Vincent MAILHOL <email@example.com>
Cc: Marc Kleine-Budde <firstname.lastname@example.org>,
Subject: Re: [PATCH v3 1/2] can: netlink: prevent incoherent can configuration in case of early return
Date: Tue, 14 Sep 2021 14:13:05 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On 14.09.21 13:45, Vincent MAILHOL wrote:
>> However, one driver fails to check the return value of open_candev():
>> So, for this particular driver, we can send incoherent values to the device.
>>> The code with all the sanity checks is already pretty complex IMO.
>>> I wonder if this effort is worth it.
>> Well, I was thinking "this is a bug so let's fix it". But your
>> argument is fair. I also did not like how complex the code was
>> getting when trying to fix that. I guess that this bug is
>> acceptable. I will leave it as it is.
>> Now, I am just worried about the softing driver.
IMO this should not be a problem.
The code is only used for a *restart* of the CAN interface. Therefore
the bitrates have been checked at the original (first) start.
> Actually, the softing driver is not CAN-FD capable.
> So there was probably no real needs to worry.
Yes. I luckily checked the other mails in the inbox before answering
next prev parent reply other threads:[~2021-09-14 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 16:03 [PATCH v3 0/2] prevent incoherent can configuration in case of early return in the CAN netlink interface Vincent Mailhol
2021-09-06 16:03 ` [PATCH v3 1/2] can: netlink: prevent incoherent can configuration in case of early return Vincent Mailhol
2021-09-07 2:05 ` Vincent MAILHOL
2021-09-07 12:51 ` Vincent MAILHOL
2021-09-08 11:41 ` Oliver Hartkopp
2021-09-14 9:35 ` Vincent MAILHOL
2021-09-14 11:45 ` Vincent MAILHOL
2021-09-14 12:13 ` Oliver Hartkopp [this message]
2021-09-06 16:03 ` [PATCH v3 2/2] can: bittiming: change can_calc_tdco()'s prototype to not directly modify priv Vincent Mailhol
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).