Skip to content

Instantly share code, notes, and snippets.

@immolo
Created October 30, 2024 06:29
Show Gist options
  • Select an option

  • Save immolo/020d28b4a111f81d0276d234790fcc9d to your computer and use it in GitHub Desktop.

Select an option

Save immolo/020d28b4a111f81d0276d234790fcc9d to your computer and use it in GitHub Desktop.
This is a reproducer for the nghttp3 bug using catalyst as the trigger.
The chroot has all the required files in the correct places. All that is required is to follow along to trace the break.
I have also created the binaries for the first run to save time being wasted using a portage snapshot from 2024-09-10
1. Download the tarball https://f.xarv.dev/~immolo/nghttp3.tar.xz md5sum 209438ecf7d39ef267266c32c7d1a0ff nghttp3.tar.xz
2. Extract where you wish (I use ~/chroot)
4. cp /etc/resolv.conf ~/chroot/nghttp3/etc
5. arch-chroot ~/chroot/nghttp3
6. nano /etc/catalyst/catalyst.conf
7. Adjust jobs and load-average options to your system (Currently set to 16 jobs and loadevg 32)
8. cd /var/tmp/catalyst
9. nano installcd-stage1.spec
10. Replace the option after snapshot_treeish: with the next commit date needed to be run
So cd96ec5e84b7c55ddd4f9156d1ff98466d770428 would become 559161160a3bdd4594b4bc0a2dfbcdb978b53118 as an example of the first one
(Tip: You can press end on the snapshot_treeish line then alt+backspace to quick deleting to allow a middle click paste.)
11. catalyst -af installcd-stage1.spec
12. goto 10 and replace commit id with next in list
At a best guess I think 2024-10-01 is where the issue is caused but as I can't prove this I have provided from the first known safe point.
Tip: The system is chrootable/viewable at each stage from /var/tmp/catalyst/tmp/23.0-default/livecd-stage1-amd64/ but the old one gets wipped each time you run the catalyst -af command.
Portage Snapshots and dates:
2024-09-10 - cd96ec5e84b7c55ddd4f9156d1ff98466d770428 - This one is prerun
2024-09-11 - 559161160a3bdd4594b4bc0a2dfbcdb978b53118
2024-09-18 - 48fabc348d8b52e608785bee45a993c6b77f6d3b
2024-09-16 - 35c563d355f114004b5fdebe6ab258daa92a51e2
2024-09-21 - b96ae6332705856122bb98beaca02f27efd11a24
2024-09-22 - 0e631d4a200a969715d43dd76cbe1e33bb49a4c6
2024-09-23 - 04dba1fdac70640331d203662b69aab9f5119dc4
2024-10-01 - a5db8b84ccfed11eea44ed51c516ecaf02f49505 - This where I think the issuue starts
2024-10-02 - dd679dfc7d18ce0db650bef30b83dbe7c3fa5679
2024-10-15 - a1f9984d5983e511de8f5d11ca3bf841c1355246 - Break is shown
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment