Osmocom Open Build Service

libosmocore.spec Changed

commit_59753c57a5d084549b43e63e3f0a0f6b4d21d766.txt Added

commit_e8cf6c6430d5288fab4bc252a485b6c0dc7bb370.txt Deleted

libosmocore_1.10.0.39.e8cf.dsc -> libosmocore_1.10.0.40.5975.dsc Changed

@@ -2,7 +2,7 @@
 Source: libosmocore
 Binary: libosmocore, libosmocodec4, libosmocodec-doc, libosmocoding0, libosmocoding-doc, libosmocore22, libosmocore-doc, libosmogb14, libosmogb-doc, libosmogsm20, libosmogsm-doc, libosmoisdn0, libosmoisdn-doc, libosmovty13, libosmovty-doc, libosmoctrl0, libosmoctrl-doc, libosmosim2, libosmosim-doc, libosmousb0, libosmousb-doc, libosmocore-dev, libosmocore-utils, libosmocore-dbg
 Architecture: any all
-Version: 1.10.0.39.e8cf
+Version: 1.10.0.40.5975
 Maintainer: Osmocom team <openbsc@lists.osmocom.org>
 Homepage: https://projects.osmocom.org/projects/libosmocore
 Standards-Version: 3.9.8
@@ -35,8 +35,8 @@
  libosmovty-doc deb doc optional arch=all
  libosmovty13 deb libs optional arch=any
 Checksums-Sha1:
- 1cdb0ac4ea900a9359379134284ac2506d80c4d5 1122844 libosmocore_1.10.0.39.e8cf.tar.xz
+ 7f05c5c958908aaff37e49f84fca6859208c458d 1123280 libosmocore_1.10.0.40.5975.tar.xz
 Checksums-Sha256:
- d1af6a3cb361c8ac2d0c82361f123e15179f0634c3fc7dc4cdcd573228d1ef31 1122844 libosmocore_1.10.0.39.e8cf.tar.xz
+ fde1e6a6ca91f48e4e6a7c957c551911f982202216b5bd8ef57947eb4d1edd3a 1123280 libosmocore_1.10.0.40.5975.tar.xz
 Files:
- 33faa9adef03f636765f11d0a35e60e3 1122844 libosmocore_1.10.0.39.e8cf.tar.xz
+ 75968df793b2371ed3aa96e5460d40b8 1123280 libosmocore_1.10.0.40.5975.tar.xz

libosmocore_1.10.0.39.e8cf.tar.xz/.tarball-version -> libosmocore_1.10.0.40.5975.tar.xz/.tarball-version Changed

libosmocore_1.10.0.39.e8cf.tar.xz/debian/changelog -> libosmocore_1.10.0.40.5975.tar.xz/debian/changelog Changed

libosmocore_1.10.0.39.e8cf.tar.xz/src/core/osmo_io.c -> libosmocore_1.10.0.40.5975.tar.xz/src/core/osmo_io.c Changed

@@ -994,12 +994,22 @@
 
 /*! Request notification of the user if/when a client socket is connected.
  *  Calling this function will request osmo_io to notify the user (via
- *  write call-back) once a non-blocking outbound connect() of the
- *  socket completes.
+ *  write call-back with res=0 and msgb=NULL) once a non-blocking outbound
+ *  connect() of the socket completes.
  *
  *  This only works for connection oriented sockets in either
  *  OSMO_IO_FD_MODE_READ_WRITE or OSMO_IO_FD_MODE_RECVMSG_SENDMSG mode.
  *
+ * The fact that the write call-back is called with msgb=NULL can be used to
+ * distinguish before this "connected" notification and a socket write failure.
+ *
+ * If the server transmits data quick enough after accepting the connection,
+ * it may happen that a read call-back is triggered towards the user before this
+ * special write-callback, since both events may come together from the kernel.
+ * Hence under those scenarios where server starts the communication, it is
+ * important not to assume or require that the write-callback(res=0, msgb=NULL)
+ * will be the first one triggered.
+ *
  *  \paramin iofd the file descriptor */
 void osmo_iofd_notify_connected(struct osmo_io_fd *iofd)
 {

Changes of Revision 381