Same for bionic 1.6.12:

openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC)           = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC)           = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0

end of run:

close(5) = 0
close(4) = 0
close(3) = 0

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.

  APT unlocks in same order as it locks

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Disco:
  Fix Committed

Bug description:
  APT releases the locks in the same order it acquires them, rather than 
reverse order. Given that we have no waiting for locks, this is not _super_ 
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, 
rather than lock-frontend.

  [Test case]
  Watch lock release with strace and see that it unlocks the right way.

  [Regression potential]
  Some other locking races or something?

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to