From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 205533] New: The flexcan/socketcan driver does not block and returns an error if all buffers are in use on transmit.
Date: Fri, 15 Nov 2019 08:21:36 -0800 [thread overview]
Message-ID: <20191115082136.70074fd0@hermes.lan> (raw)
Begin forwarded message:
Date: Thu, 14 Nov 2019 17:10:29 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 205533] New: The flexcan/socketcan driver does not block and returns an error if all buffers are in use on transmit.
https://bugzilla.kernel.org/show_bug.cgi?id=205533
Bug ID: 205533
Summary: The flexcan/socketcan driver does not block and
returns an error if all buffers are in use on
transmit.
Product: Networking
Version: 2.5
Kernel Version: 4.14.149
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: brian.j.cody@gmail.com
Regression: No
When the output buffer is saturated, even if the socket is set up for blocking
use, a "write" to the CAN socket may result in a -1 return value with errno set
to 105 (ENOBUFS).
The socket is created using socket(PF_CAN, SOCK_RAW, CAN_RAW). SO_SNDBUF is set
to 2240. fcntl is used to disable O_NONBLOCK.
I see the error case after "many" sends. In this situation three separate
processes are sharing the CAN bus on the local processor. The error only occurs
when all processes are heavily using the bus (set at 1 MHz), and there does not
appear to be a normal re-entrancy issue with the driver.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-11-15 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191115082136.70074fd0@hermes.lan \
--to=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).