Attention is currently required from: laforge.
pespin has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/libosmo-netif/+/41666?usp=email )
Change subject: cosmetic: stream_srv: srv_link: Document no need for OSMO_SOCK_F_NONBLOCK
......................................................................
Patch Set 3:
This change is ready for review.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-netif/+/41666?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-netif
Gerrit-Branch: master
Gerrit-Change-Id: I98a6ef55a0a7289b9eeb7e8062e9afa4d87f51eb
Gerrit-Change-Number: 41666
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Mon, 15 Dec 2025 16:15:29 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/libosmocore/+/41671?usp=email )
Change subject: io_uring: RECVMSG_SENDMSG: Reset fd to blocking after osmo_fd_register() workaround
......................................................................
io_uring: RECVMSG_SENDMSG: Reset fd to blocking after osmo_fd_register() workaround
When IOFD_FLAG_NOTIFY_CONNECTED is requested by the user through
osmo_iofd_notify_connected(), a write_cb(0, NULL) callback is done
towards the user to notify the socket is connected.
In mode RECVMSG_SENDMSG, at least for SCTP sockets, according to comment
in iofd_uring_register() (see also OS#5751) we cannot do the write(0)
trick to get notifications, so instead we need to workaround by using a
temporary osmo_fd to poll() for write status.
To do so, we call osmo_fd_register(), which internally sets the fd as
non-blocking (O_NONBLOCK). However, this is becomes an undesired
behavior later on when connect happens and io_uring is used to
recvmsg/sendmsg, since that could cause sqes to be answered with -EAGAIN
cqes at the kernel isntead of keeping (blocking) them internally until
the transaction can be resolved. This seems was a "desired" or
"expected" behavior in older kernels according to public
discussions/tickets, but it seeems it changed over time (see eg. GH#364
below).
In summary, the conclusion seems to be: try to avoid as much as possible mixing
O_NONBLOCK with io_uring, as you may get totally unexpected/changing
behavior.
Hence, avoid keeping O_NONBLOCK for those sockets when moving back from
osmo_fd to io_uring.
See regarding related discussion on the expected behavior with io_uring and O_NONBLOCK:
https://www.spinics.net/lists/io-uring/msg04058.htmlhttps://github.com/axboe/liburing/issues/364
Change-Id: Idba623730230bc049b827e51b058cd64d23b730f
---
M src/core/osmo_io_uring.c
1 file changed, 21 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/71/41671/1
diff --git a/src/core/osmo_io_uring.c b/src/core/osmo_io_uring.c
index cac6272..278b686 100644
--- a/src/core/osmo_io_uring.c
+++ b/src/core/osmo_io_uring.c
@@ -534,6 +534,23 @@
static void iofd_uring_write_enable(struct osmo_io_fd *iofd);
static void iofd_uring_read_enable(struct osmo_io_fd *iofd);
+/* make an FD blockig:
+ * osmo_fd_register(ofd) did set fd flag O_NONBLOCK previously. We don't
+ * want to keep the fd as O_NONBLOCK once we start using io_uring,
+ * otherwise we'd end up getting cqes with -EAGAIN; better let the kernel
+ * wait internally for the sqe to complete. */
+static int iofd_reset_fd_blocking(int fd)
+{
+ int flags;
+
+ /* make FD nonblocking */
+ flags = fcntl(fd, F_GETFL);
+ if (flags < 0)
+ return flags;
+ flags &= ~O_NONBLOCK;
+ flags = fcntl(fd, F_SETFL, flags);
+ return flags;
+}
/* called via osmocom poll/select main handling once outbound non-blocking connect() completes */
static int iofd_uring_connected_cb(struct osmo_fd *ofd, unsigned int what)
@@ -547,6 +564,7 @@
/* Unregister from poll/select handling. */
osmo_fd_unregister(ofd);
+ iofd_reset_fd_blocking(ofd->fd);
IOFD_FLAG_UNSET(iofd, IOFD_FLAG_NOTIFY_CONNECTED);
/* Notify the application about this via a zero-length write completion call-back. */
@@ -591,7 +609,8 @@
* Use a temporary osmo_fd which we can use to notify us once the connection is established
* or failed (indicated by FD becoming writable). This is needed as (at least for SCTP sockets)
* one cannot submit a zero-length writev/sendmsg in order to get notification when the socket
- * is writable.*/
+ * is writable.
+ * NOITE: osmo_fd_setup() sets iofd->fd as O_NONBLOCK. */
if (IOFD_FLAG_ISSET(iofd, IOFD_FLAG_NOTIFY_CONNECTED)) {
osmo_fd_setup(&iofd->u.uring.connect_ofd, iofd->fd, OSMO_FD_WRITE,
iofd_uring_connected_cb, iofd, 0);
@@ -664,6 +683,7 @@
if (IOFD_FLAG_ISSET(iofd, IOFD_FLAG_NOTIFY_CONNECTED)) {
osmo_fd_unregister(&iofd->u.uring.connect_ofd);
+ iofd_reset_fd_blocking(iofd->u.uring.connect_ofd.fd);
IOFD_FLAG_UNSET(iofd, IOFD_FLAG_NOTIFY_CONNECTED);
}
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/41671?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Idba623730230bc049b827e51b058cd64d23b730f
Gerrit-Change-Number: 41671
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/libosmocore/+/41670?usp=email )
Change subject: cosmetic: io_uring: Fix typo in comment
......................................................................
cosmetic: io_uring: Fix typo in comment
Change-Id: I5ff1248e8aff1b55c65aecee4d1e2f5c0d5a48fb
---
M src/core/osmo_io_uring.c
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/70/41670/1
diff --git a/src/core/osmo_io_uring.c b/src/core/osmo_io_uring.c
index e4a87ad..cac6272 100644
--- a/src/core/osmo_io_uring.c
+++ b/src/core/osmo_io_uring.c
@@ -590,7 +590,7 @@
/* OSMO_IO_FD_MODE_RECVMSG_SENDMSG:
* Use a temporary osmo_fd which we can use to notify us once the connection is established
* or failed (indicated by FD becoming writable). This is needed as (at least for SCTP sockets)
- * one cannot submit a zero-length writev/sendmsg in order to get notification when the socekt
+ * one cannot submit a zero-length writev/sendmsg in order to get notification when the socket
* is writable.*/
if (IOFD_FLAG_ISSET(iofd, IOFD_FLAG_NOTIFY_CONNECTED)) {
osmo_fd_setup(&iofd->u.uring.connect_ofd, iofd->fd, OSMO_FD_WRITE,
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/41670?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I5ff1248e8aff1b55c65aecee4d1e2f5c0d5a48fb
Gerrit-Change-Number: 41670
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Attention is currently required from: fixeria.
pespin has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmocom-bb/+/41652?usp=email )
Change subject: trx_toolkit: print milliseconds in logging
......................................................................
Patch Set 1: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/41652?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: I7c53149f4e678670392773bbcf9648997ba4ff1b
Gerrit-Change-Number: 41652
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 15 Dec 2025 12:26:08 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Attention is currently required from: fixeria.
pespin has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmocom-bb/+/41652?usp=email )
Change subject: trx_toolkit: print milliseconds in logging
......................................................................
Patch Set 1:
(1 comment)
File src/target/trx_toolkit/app_common.py:
https://gerrit.osmocom.org/c/osmocom-bb/+/41652/comment/72c9f9ff_64c81a16?u… :
PS1, Line 42: log_fmt = "%(asctime)s.%(msecs)03d " + log_fmt if log_time else log_fmt
> There exists no macro for usec granularity, so this would require writing a custom logging formatter […]
Let's then merge this one for now.
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/41652?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: I7c53149f4e678670392773bbcf9648997ba4ff1b
Gerrit-Change-Number: 41652
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 15 Dec 2025 12:26:02 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Attention is currently required from: pespin.
fixeria has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmocom-bb/+/41652?usp=email )
Change subject: trx_toolkit: print milliseconds in logging
......................................................................
Patch Set 1:
(1 comment)
File src/target/trx_toolkit/app_common.py:
https://gerrit.osmocom.org/c/osmocom-bb/+/41652/comment/6bdac25e_e962e6f1?u… :
PS1, Line 42: log_fmt = "%(asctime)s.%(msecs)03d " + log_fmt if log_time else log_fmt
> is it easy to print usecs instead? I'd welcome usec granularity.
There exists no macro for usec granularity, so this would require writing a custom logging formatter. I can work on adding it if you really-really need that.
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/41652?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: I7c53149f4e678670392773bbcf9648997ba4ff1b
Gerrit-Change-Number: 41652
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 15 Dec 2025 12:04:45 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/41661?usp=email )
Change subject: cosmetic: bts-trx: fix typo in comment
......................................................................
cosmetic: bts-trx: fix typo in comment
Change-Id: Ibe589f4d26899d92560a60751f62bd5e8380835a
---
M src/osmo-bts-trx/trx_provision_fsm.c
1 file changed, 1 insertion(+), 1 deletion(-)
Approvals:
Jenkins Builder: Verified
osmith: Looks good to me, approved
diff --git a/src/osmo-bts-trx/trx_provision_fsm.c b/src/osmo-bts-trx/trx_provision_fsm.c
index 5ca23e3..7ed617a 100644
--- a/src/osmo-bts-trx/trx_provision_fsm.c
+++ b/src/osmo-bts-trx/trx_provision_fsm.c
@@ -400,7 +400,7 @@
switch (event) {
case TRX_PROV_EV_CLOSE:
/* In this state, we didn't for sure send a POWERON yet, hence we
- are save directly applying the close as if we received a
+ are safe directly applying the close as if we received a
POWEROFF RSP: */
if (pinst->num == 0)
trx_prov_fsm_apply_close(pinst->phy_link, 0);
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/41661?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: merged
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Ibe589f4d26899d92560a60751f62bd5e8380835a
Gerrit-Change-Number: 41661
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>