1. 10 Oct, 2019 1 commit
    • anonym's avatar
      Test suite: only partially fill memory for userspace processes. · c6838f36
      anonym authored
      Filling all memory often leads to the VM crashing. So why fill all
      memory? Back when Tails was 32-bit (or mixed with 64-bit) there were
      some of uncertainty around the 4 GiB limit, which motivated us to fill
      a larger region than 4 GiB, so without much thought we might have just
      gone ahead and filled all of it. But, AFAICT, if we went with the
      approach I describe above and allocated >4 GiB then the test would
      still have done what we wanted.
      
      In today's fully 64-bit world we have no reason for allocating >4 GiB,
      so we could go with 128 MiB like the other tests arbitrarily (?) do.
      
      Will-fix: #17104
      c6838f36
  2. 11 Jul, 2019 2 commits
  3. 18 Jun, 2019 1 commit
  4. 24 May, 2019 1 commit
  5. 03 Jan, 2018 1 commit
  6. 18 May, 2017 2 commits
    • intrigeri's avatar
      Return to the initramfs (unpacked in /run/initramfs) on shutdown (refs:... · 888ccc5a
      intrigeri authored
      Return to the initramfs (unpacked in /run/initramfs) on shutdown (refs: #12428, #12354, Debian#778849).
      
      … otherwise the aufs read-write (tmpfs) branch, among possibly other things,
      can't be properly unmounted and its content remains in memory.
      
      Notes:
      
       * We have to handle some unmounting ourselves in initramfs-pre-shutdown-hook:
         systemd-shutdown doesn't manage to unmount the aufs read-write
         branch (/oldroot/lib/live/mount/overlay) as it is needed by the
         aufs (/oldroot) filesystem, and reciprocally it cannot unmount /oldroot as it
         is kept busy by /oldroot/lib/live/mount/*. So we disentangle this mess
         ourselves. And we have to manually empty the aufs read-write (tmpfs) branch,
         otherwise for some reason its content remains in memory. This code will of
         course need to be adapted for overlayfs some day.
      
       * We lock /bin/kill in memory: apparently systemd-exit.service needs it.
      
       * We remount /run on shutdown *before* dropping caches, just in case dropping
         caches removes what we've locked into memory.
      
       * We unpack the initramfs to /run/initramfs at *boot* time: sadly, I was not
         able to have it unpacked reliably in udev-watchdog-wrapper when the boot
         medium is ejected, so we'll use a little bit more RAM (instead of locking the
         compressed initramfs into memory, we're storing the uncompressed one there)
         and probably slow down the boot a bit, in order to make emergency shutdown
         robust. Note, however, that we save some of the RAM used by the uncompressed
         initramfs by deleting the worst offenders (kernel modules).
      
       * For now the whole procedure is quite noisy on the screen: the pre-shutdown
         hook runs under "set -x", doesn't run "clear", and spits out lots of
         debugging information. The goal is to enable users to provide useful
         debugging data if they have problems with emergency shutdown. Once we have
         shipped this code in a few releases and trust it's robust enough, we can
         surely reconsider and polish the UX by making the output less noisy.
      
       * We use absolute paths in many places to avoid $PATH lookup which might
         fail if the root filesystem is not there anymore.
      888ccc5a
    • intrigeri's avatar
  7. 05 Apr, 2017 9 commits
  8. 26 Aug, 2016 4 commits
  9. 30 Jul, 2016 1 commit
  10. 18 Dec, 2015 2 commits
  11. 09 Dec, 2015 1 commit
  12. 01 Aug, 2015 1 commit
  13. 03 Oct, 2014 1 commit
  14. 01 Jan, 2014 1 commit
  15. 28 Dec, 2013 4 commits
  16. 03 Apr, 2013 1 commit
    • Tails developers's avatar
      Make Tails shutdown steps less confusing. · ef0b9914
      Tails developers authored
      The `I safely shutdown Tails` and `I shutdown Tails` were both
      confusing names considering what they do. Merging the former into the
      step when we wait for the memory wipe to finish, and renaming the
      latter to say "completley" as in "we also wait until the computer
      shuts down completely" hopefully make this clearer.
      ef0b9914
  17. 27 Mar, 2013 1 commit
    • Tails developers's avatar
      Reorganise features/, unifying both test suites. · 375216ce
      Tails developers authored
      Now all .feature:s reside directly in the root of features/, and they
      are differentiated with tags: source tests are tagged '@source' and
      product (i.e. Tails ISO image) tests are tagged '@product'. These tags
      then set up the appropriate environment on a feature-by-feature basis.
      375216ce
  18. 18 Mar, 2013 1 commit
    • Tails developers's avatar
      Split step. · 371d63c3
      Tails developers authored
      At some point we want to "unsafely" shutdown Tails via an emergency
      shutdown.
      371d63c3
  19. 08 Mar, 2013 4 commits
  20. 26 Feb, 2013 1 commit