Ubuntu's stable release policy requires that only known-good bug fixes be introduced to the LTS releases, not whole version jumps of packages. So no, by policy Ubuntu would not update libmaxminddb from 1.3.x to 1.4.x.
However, we do assist in getting specific patches extracted from upstream releases and backported, if they can be properly reproduced and verified safe. I think your crash definitely qualifies if we can isolate the patch. However, if it's not crashing on 20.04, this suggests a fix does exist... somewhere... it's just a matter now of finding it. If you have access to the core files or can reproduce the issue on your end, a straightforward next action you could take would be to get a more complete stacktrace. Install symbols for nginx and libmaxminddb, then load the core into gdb and then get a `backtrace full`. Some tips on how to do this are at: * https://wiki.ubuntu.com/Backtrace * https://wiki.ubuntu.com/DebuggingProgramCrash For stable release updates (SRU's) it's required to have steps to reproduce. You mentioned you don't know the IP address; if it still does not show in the full backtrace collected above, then you might try adjusting nginx logging parameters or even running strace. --- Your stacktrace mentions MMDB_lookup_sockaddr () as the nearest routine to the point of crash. The git blame for the 1.4.2 version of that file shows only commit 0cc6caec as a difference, but that change doesn't appear likely to to be a crash fix; perhaps the fix is for whatever frame #0 or #1 of your backtrace is. This routine has separate branches of logic for ipv4 addresses from ipv6. Perhaps ipv6 addresses would reproduce it? It looks like there are only about 100 change entries between 1.3.1 and 1.4.2 (`git log 1.3.1..1.4.2`), most of which are not bugfixes. Unfortunately none of the commits jump out to me as obvious fixes for this bug. But maybe with a more complete backtrace and steps to reproduce the problem the fix will be more obvious. ** Changed in: libmaxminddb (Ubuntu) Status: New => Incomplete ** Summary changed: - Certain Nginx requests cause a Bus error + Certain Nginx requests cause a Bus error (18.04 only) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935673 Title: Certain Nginx requests cause a Bus error (18.04 only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmaxminddb/+bug/1935673/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
