OsmocomBB MS-side GSM Protocol stack (L1, L2, L3) including firmware https://osmocom.org/projects/baseband
Go to file
Vadim Yanitskiy d944f1d89d trxcon/scheduler: be safe against a theoretical integer overflow
As was noted by Pau Espin Pedrol, there is a theoretical chance
that lchan->tdma.num_proc would overflow, so as a consequence,
subst_frame_loss() will be unable to compensate one
(potentionally lost) Downlink burst.

On practice, given the size of unsigned long and duration of a
single TDMA frame, it would only happen once in roughly ~6 years.

  FRAME_DURATION = 4615 * 10e-6
  ULONG_MAX = 2 ** 32 - 1

  FRAME_DURATION * ULONG_MAX -> ~198212740 seconds
                             -> ~55059 hours
                             -> ~2294 days
                             -> ~6 years.

Chances are that trxcon would crash much earlier, or even GSM
would be completely forgotten after such a long time run, but
let's work this around and simply start counting from 1
if that overflow eventually happens.

Change-Id: I3d40ef09b06039a85df52af06ab38de314e1a434
2020-03-16 10:32:42 +00:00
contrib contrib/jenkins.sh: also run unit tests for TRX Toolkit 2019-12-31 17:03:12 +00:00
doc doc/manuals: integrate into this repository 2018-12-04 12:14:59 +00:00
include l1ctl_proto.h: add extended RACH (11-bit) request message 2019-04-22 05:10:13 +07:00
src trxcon/scheduler: be safe against a theoretical integer overflow 2020-03-16 10:32:42 +00:00
.gitignore doc/manuals: integrate into this repository 2018-12-04 12:14:59 +00:00
.gitreview Add 'git review' config file 2017-09-07 12:21:24 +02:00