Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BUG/MEDIUM: stconn: Only consider I/O timers to update stream's expir…
…ation date In sc_notify(), it remained a case where it was possible to set an expiration date on the stream in the past, leading to a crash because of a BUG_ON(). This must never happen of course. In sc_notify(), The stream's expiration may be updated in case no wakeup conditions are encoutered. In that case, we must take care to never set an expiration date in the past. However, it appeared there was still a condition to do so. This code is based on an implicit postulate: the stream's expiration date must always be set when we leave process_stream(). It was true since the 2.9. But in 3.0, the buffer allocation mechanism was improved and on an alloc failure in process_stream(), the stream is inserted in a wait-list and its expiration date is set to TICK_ETERNITY. With the good timing, and an analysis expiration date set on a channel, it is possible to set the stream's expiration date in past. After analysis, it appeared that the proper way to fix the issue is to only evaluate I/O timers (read and write timeout) and not stream's timers (analase_exp or conn_exp) because only I/O timers may have changed since the last process_stream() call. This patch must be backported as far as 3.0 to fix the issue. But it is probably a good idea to also backported it as far as 2.8.
- Loading branch information