| 2009-11-05 22:41:02 |
Mike Buckley |
bug |
|
|
added bug |
| 2009-11-09 16:03:10 |
Scott James Remnant (Canonical) |
affects |
mountall (Ubuntu) |
cryptsetup (Ubuntu) |
|
| 2009-12-10 16:33:59 |
all-by-my-self |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted? |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
|
|
| 2009-12-15 07:51:07 |
Steve Langasek |
cryptsetup (Ubuntu): importance |
Undecided |
High |
|
| 2009-12-15 07:51:58 |
Steve Langasek |
summary |
/dev/mapper/tmp encrypted with /dev/urandom not mounted on bootup |
race condition between encrypted device creation and mountall probing with random-encrypted devices (swap, tmp) |
|
| 2009-12-15 20:38:17 |
Steve Langasek |
cryptsetup (Ubuntu): status |
New |
In Progress |
|
| 2009-12-15 20:51:11 |
Steve Langasek |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-12-15 20:51:11 |
Steve Langasek |
bug task added |
|
cryptsetup (Ubuntu Karmic) |
|
| 2009-12-15 20:51:41 |
Steve Langasek |
cryptsetup (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-12-15 20:51:41 |
Steve Langasek |
cryptsetup (Ubuntu Karmic): status |
New |
Triaged |
|
| 2009-12-15 20:51:41 |
Steve Langasek |
cryptsetup (Ubuntu Karmic): milestone |
|
karmic-updates |
|
| 2009-12-15 20:51:41 |
Steve Langasek |
cryptsetup (Ubuntu Karmic): assignee |
|
Steve Langasek (vorlon) |
|
| 2009-12-15 20:52:10 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/cryptsetup/ubuntu |
|
| 2009-12-16 02:15:08 |
Launchpad Janitor |
cryptsetup (Ubuntu): status |
In Progress |
Fix Released |
|
| 2009-12-16 06:45:05 |
Steve Langasek |
nominated for series |
|
Ubuntu Lucid |
|
| 2009-12-16 06:45:05 |
Steve Langasek |
bug task added |
|
cryptsetup (Ubuntu Lucid) |
|
| 2009-12-16 07:02:40 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
|
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/cryptswap /dev/sdf12 /dev/urandom swap
4. configure the swap partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/cryptswap none swap sw 0 0
5. reboot
6. verify that the swap partition is not successfully enabled (either by confirming that the system fails to boot fully, or by checking the output of 'swapon -s')
7. if necessary to boot the system, reboot to single-user mode, mount -orw,remount /, and comment out the cryptswap line from /etc/fstab
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the cryptswap line in /etc/fstab
10. reboot
11. verify that the swap partition has been successfully enabled, by checking the output of 'swapon -s' |
|
| 2009-12-16 07:11:25 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/cryptswap /dev/sdf12 /dev/urandom swap
4. configure the swap partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/cryptswap none swap sw 0 0
5. reboot
6. verify that the swap partition is not successfully enabled (either by confirming that the system fails to boot fully, or by checking the output of 'swapon -s')
7. if necessary to boot the system, reboot to single-user mode, mount -orw,remount /, and comment out the cryptswap line from /etc/fstab
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the cryptswap line in /etc/fstab
10. reboot
11. verify that the swap partition has been successfully enabled, by checking the output of 'swapon -s' |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/cryptswap /dev/sdf12 /dev/urandom swap
4. configure the swap partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/cryptswap none swap sw 0 0
5. reboot
6. verify that the swap partition is not successfully enabled (either by confirming that the system fails to boot fully, or by checking the output of 'swapon -s')
7. if necessary to boot the system, reboot to single-user mode, mount -orw,remount /, and comment out the cryptswap line from /etc/fstab
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the cryptswap line in /etc/fstab
10. reboot
11. verify that the swap partition has been successfully enabled, by checking the output of 'swapon -s'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU. |
|
| 2009-12-16 07:12:24 |
Steve Langasek |
tags |
|
regression-release |
|
| 2009-12-16 08:45:26 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/cryptswap /dev/sdf12 /dev/urandom swap
4. configure the swap partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/cryptswap none swap sw 0 0
5. reboot
6. verify that the swap partition is not successfully enabled (either by confirming that the system fails to boot fully, or by checking the output of 'swapon -s')
7. if necessary to boot the system, reboot to single-user mode, mount -orw,remount /, and comment out the cryptswap line from /etc/fstab
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the cryptswap line in /etc/fstab
10. reboot
11. verify that the swap partition has been successfully enabled, by checking the output of 'swapon -s'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU. |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the swap partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 0
5. reboot
6. verify that the tmp partition is not successfully mounted (the system should fail to boot fully)
7. if necessary to boot the system, reboot to single-user mode, mount -orw,remount /, and comment out the crypttmp line from /etc/fstab
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the crypttmp line in /etc/fstab
10. reboot
11. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
|
| 2009-12-16 09:25:55 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the swap partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 0
5. reboot
6. verify that the tmp partition is not successfully mounted (the system should fail to boot fully)
7. if necessary to boot the system, reboot to single-user mode, mount -orw,remount /, and comment out the crypttmp line from /etc/fstab
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the crypttmp line in /etc/fstab
10. reboot
11. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 0
5. reboot
6. verify that the tmp partition is not successfully mounted by running 'mount | grep /tmp'
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the crypttmp line in /etc/fstab
10. reboot
11. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
|
| 2009-12-17 08:38:04 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 0
5. reboot
6. verify that the tmp partition is not successfully mounted by running 'mount | grep /tmp'
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the crypttmp line in /etc/fstab
10. reboot
11. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 2
5. reboot
6. verify that the tmp partition is not successfully mounted by running 'mount | grep /tmp'
7. upgrade to the karmic-proposed version of cryptsetup
8. re-enable the crypttmp line in /etc/fstab
9. reboot
10. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
|
| 2009-12-17 08:41:34 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 2
5. reboot
6. verify that the tmp partition is not successfully mounted by running 'mount | grep /tmp'
7. upgrade to the karmic-proposed version of cryptsetup
8. re-enable the crypttmp line in /etc/fstab
9. reboot
10. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 2
5. ensure the device contains no other filesystem signatures by blanking it with 'dd if=/dev/zero of=/dev/sdf12 bs=$((1024*1024))'
5. reboot
6. verify that the tmp partition is not successfully mounted by running 'mount | grep /tmp'
7. upgrade to the karmic-proposed version of cryptsetup
8. re-enable the crypttmp line in /etc/fstab
9. reboot
10. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
|
| 2009-12-17 08:47:02 |
Steve Langasek |
description |
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 2
5. ensure the device contains no other filesystem signatures by blanking it with 'dd if=/dev/zero of=/dev/sdf12 bs=$((1024*1024))'
5. reboot
6. verify that the tmp partition is not successfully mounted by running 'mount | grep /tmp'
7. upgrade to the karmic-proposed version of cryptsetup
8. re-enable the crypttmp line in /etc/fstab
9. reboot
10. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my /etc/crypttab I have:
tmp /dev/sda2 /dev/urandom tmp
swap /dev/sda3 /dev/urandom swap
In my /etc/fstab I have (among other lines), this:
/dev/mapper/tmp /tmp ext2 relatime 0 2
Most of the time the system boots OK, but /tmp never gets mounted.
This appears to be an issue with mountall because if I run mountall from the command line, then /tmp does get mounted.
When the /dev/mapper/tmp device is created (part of the cryptsetup process), the mkfs -t ext2 command is run on /dev/mapper/tmp. It appears mountall is not waiting for this to complete. Should there be a timeout for a dynamically created tmp to be available before it is mounted?
TEST CASE:
1. select a spare partition on your disk, referred to below as /dev/sdf12
2. install the cryptsetup package from karmic.
3. configure it for use with cryptsetup as a device with a random key by adding this line to /etc/crypttab:
/dev/mapper/crypttmp /dev/sdf12 /dev/urandom tmp
4. configure the tmp partition to be auto-enabled by adding this line to /etc/fstab:
/dev/mapper/crypttmp /tmp ext2 defaults 0 2
5. ensure the device contains no other filesystem signatures by blanking it with 'dd if=/dev/zero of=/dev/sdf12 bs=$((1024*1024))'
5. reboot
6. verify that the tmp partition is not successfully mounted: mountall should refuse to continue booting the system because the device is unavailable.
7. boot into the rescue shell to comment out the tmp line from /etc/fstab, then reboot
8. upgrade to the karmic-proposed version of cryptsetup
9. re-enable the crypttmp line in /etc/fstab
10. reboot
11. verify that the tmp partition has been successfully mount, by checking the output of 'mount | grep /tmp'
REGRESSION POTENTIAL:
In order to prevent mountall from seeing the block device before it's been formatted / mkswap'ed for use, cryptsetup must create the device under a different name initially, format, and then rename to the public device name. For sanity's sake, the proposed patch does this for /all/ cryptsetup devices, not just those configured for tmp or swap; and there is a small but finite risk that someone will already have a /dev/mapper/${name}_unformatted node on their system that conflicts with one of these devices, causing this device to fail to be set up at boot time due to the name collision.
The '${name}_unformatted' temp name was chosen to minimize this risk; I believe the risk is acceptably low for an SRU.
|
|
| 2009-12-18 11:56:36 |
Martin Pitt |
cryptsetup (Ubuntu Karmic): status |
Triaged |
Fix Committed |
|
| 2009-12-18 11:56:45 |
Martin Pitt |
tags |
regression-release |
regression-release verification-needed |
|
| 2009-12-21 00:25:49 |
Swâmi Petaramesh |
attachment added |
|
mountall log with /tmp mounting http://launchpadlibrarian.net/37002951/.mountall-1.log |
|
| 2009-12-21 00:26:33 |
Swâmi Petaramesh |
attachment added |
|
mountall log with /tmp NOT mounting http://launchpadlibrarian.net/37002956/.mountall-2.log |
|
| 2009-12-22 01:13:05 |
Steve Langasek |
tags |
regression-release verification-needed |
regression-release verification-failed |
|
| 2009-12-22 01:39:28 |
Steve Langasek |
cryptsetup (Ubuntu Karmic): status |
Fix Committed |
In Progress |
|
| 2009-12-22 01:39:32 |
Steve Langasek |
cryptsetup (Ubuntu Lucid): status |
Fix Released |
In Progress |
|
| 2009-12-22 21:52:15 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/cryptsetup/karmic |
|
| 2009-12-22 23:30:09 |
Launchpad Janitor |
cryptsetup (Ubuntu Lucid): status |
In Progress |
Fix Released |
|
| 2009-12-22 23:49:53 |
Steve Langasek |
tags |
regression-release verification-failed |
regression-release |
|
| 2009-12-23 10:16:17 |
Martin Pitt |
cryptsetup (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-12-23 10:16:24 |
Martin Pitt |
tags |
regression-release |
regression-release verification-needed |
|
| 2009-12-24 17:26:56 |
Steve Langasek |
tags |
regression-release verification-needed |
regression-release verification-done |
|
| 2010-01-14 12:14:56 |
Launchpad Janitor |
cryptsetup (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2010-02-15 19:17:31 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cryptsetup |
|
| 2010-02-20 03:45:23 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-updates/cryptsetup |
|
| 2010-06-18 22:57:54 |
Johannes Mockenhaupt |
removed subscriber Johannes Mockenhaupt |
|
|
|
| 2010-07-11 08:24:26 |
Launchpad Janitor |
branch linked |
|
lp:debian/sid/cryptsetup |
|
| 2011-02-15 11:59:12 |
kapetr |
attachment added |
|
monitor screenshot - cryptswap https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/475936/+attachment/1851280/+files/shot0002.png |
|
| 2011-10-16 06:58:22 |
Dejan |
bug |
|
|
added subscriber Dejan |
| 2013-11-01 16:56:30 |
Launchpad Janitor |
branch linked |
|
lp:~xnox/debian/sid/cryptsetup/ubuntu |
|
