Bug 1524083 - 4.14.4-200.fc26 breaks Apache Trafficserver
Summary: 4.14.4-200.fc26 breaks Apache Trafficserver
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: trafficserver
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan-Frode Myklebust
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-10 02:13 UTC by Harald Reindl
Modified: 2018-05-29 11:32 UTC (History)
20 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:32:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Harald Reindl 2017-12-10 02:13:27 UTC
everything but apache trafficserver works - https://github.com/apache/trafficserver/issues/2908 

while this is sure a bug in trafficserver the kernel "don't break userspace" rule shouldn't lead to such an issue given that ATS 7.1.1 is out now for a longer time 

for now excluded 4.14 from the proxy machine, everything else works fine

Comment 1 Laura Abbott 2017-12-11 22:18:44 UTC
The change is caused by commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=04e35f4495dd560db30c25efca4eecae8ec8c375 . Based on discussions with the patch author (Kees Cook), what's happening is the stack limit once got lowered so future attempts to set it to ulimited are breaking the call to setrlimit.

The userspace checking here is pretty buggy though. Relying on setulimit to always succeed is asking for trouble. Kees also noted the check is incorrect (should be checking r.rlim_cur != r.rlim_max). The behavior of no kernel regressions doesn't apply to buggy programs so I don't think there is anything for the kernel to fix here. I moved this to trafficserver for it to get fixed there.

Comment 2 Harald Reindl 2017-12-11 22:49:52 UTC
that's why i just commented but kept my +1 bodhi karma - it needs to be fixed somehow in the near future since 4.13 is EOL

Comment 3 Harald Reindl 2017-12-15 14:42:40 UTC
https://github.com/apache/trafficserver/commit/0cdb610c311ccc9f67c9cf83460a8a11976e4e1b.patch

[root@proxy:~]$ uname -r
4.14.4-200.fc26.x86_64

[root@proxy:~]$ rpm -q trafficserver
trafficserver-7.1.1-4.0.fc26.20171214.rh.sandybridge.x86_64

Comment 4 Fedora End Of Life 2018-05-03 08:05:29 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2018-05-29 11:32:04 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.