ecryptfs_readpage: Error decrypting page

[starslights]

Hello,

I run Kubuntu Karmic 9.10 on x86 64 with ecryptfs and i have error in my log .

 kernel: [36040.294266] ecryptfs_read_lower: octets_read = [-4]; expected [4096]
 kernel: [36040.294271] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-22]
 kernel: [36040.294274] ecryptfs_readpage: Error decrypting page; rc = [-22]
kernel: [36040.294284] ecryptfs_read_lower: octets_read = [-4]; expected [4096]

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: moonlights 3584 F.... knotify4
                      moonlights 3619 F.... kmix
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
   Mixer name : 'Analog Devices AD1989B'
   Components : 'HDA:11d4989b,10438311,00100300'
   Controls : 48
   Simple ctrls : 27
Date: Sun Nov 29 18:11:38 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=83c95442-a3bb-41ea-9822-97768074dcbf
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: System manufacturer P5Q-E
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-15-generic 2.6.31-15.50
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=d4f7b656-5965-43fb-acc2-5bc98e3ba8c6 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=fr_CH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-15-generic N/A
 linux-firmware 1.25
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-15-generic x86_64
XsessionErrors: (polkit-gnome-authentication-agent-1:3631): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 02/25/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd02/25/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Jeremy Foshee (jeremyfoshee)]

Hi starslights,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 490005

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[starslights (starslights)]

Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: moonlights 3218 F.... knotify4
                      moonlights 3277 F.... kmix
                      moonlights 20533 F.... mplayer
 /dev/snd/pcmC0D0p: moonlights 20533 F...m mplayer
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
   Mixer name : 'Analog Devices AD1989B'
   Components : 'HDA:11d4989b,10438311,00100300'
   Controls : 48
   Simple ctrls : 27
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=83c95442-a3bb-41ea-9822-97768074dcbf
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: System manufacturer P5Q-E
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-21-generic root=UUID=d4f7b656-5965-43fb-acc2-5bc98e3ba8c6 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_CH.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-21-generic N/A
 linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/25/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd02/25/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[starslights (starslights)]

Hi Jeremy,

The bug still on my system, i run the more recent kernel on my kubuntu karmic 9.10 like you will see in my last apport.

 i will look if in Lucid this same bug still and keep in touch.

Best regards

Stars

Linux xxxxxx 2.6.31-21-generic #59-Ubuntu SMP Wed Mar 24 07:28:27 UTC 2010 x86_64 GNU/Linux

[Gioele Barabucci (gioele)]

This problem seems to be linked to <https://bugs.launchpad.net/ecryptfs/+bug/509180>.

It is still present in lucid's 2.6.32-25-generic.

The new dmesg output is

    [ 3612.860813] ecryptfs_readpage: Error decrypting page; rc = [-4]
    [ 3612.860818] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
    [ 3612.860821] ecryptfs_readpage: Error decrypting page; rc = [-4]
    [ 3613.036296] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    [ 3613.036362] Valid eCryptfs headers not found in file header region or xattr region
    [ 3613.036366] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO

[Paolo Bonzini (bonzini)]

I am seeing these messages whenever I have two processes reading the same file. Note that write access is not necessary.

The simplest way to reproduce it is

    git grep abczzz & git grep abczzz

but this is probably because git uses multiple threads, rather than because the bug is related to git. In fact, I reproduced it in places where I have not even moved the HEAD of this repository since I copied it from an unencrypted directory to an ecryptfs one.

Another way to reproduce it for me (but much less consistently) is:

    (find . -type f | xargs md5sum > /dev/null) & find . -type f | xargs md5sum > /dev/null

which gives occasional Input/Output errors. In some cases (and especially with git grep) instead the program sees an empty file (confirmed with strace) which shows as

    error: 'Documentation/HOWTO': short read Success
    error: 'Documentation/arm/tcm.txt': short read Success
    error: 'Documentation/braille-console.txt': short read Success

At the same time, the dreaded messages appear in /var/log/messages

    Dec 7 16:55:54 yakj kernel: [32510.145170] ecryptfs_readpage: Error decrypting page; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145180] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145182] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145184] ecryptfs_readpage: Error decrypting page; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145198] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145231] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145235] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145245] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145285] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:55:54 yakj kernel: [32510.145320] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:59:56 yakj kernel: [32752.032531] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
    Dec 7 16:59:56 yakj kernel: [32752.032550] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
    Dec 7 17:01:11 yakj kernel: [32827.829724] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO

[klerfayt (klerfayt-deactivatedaccount)]

Is this bug dangerous to the integrity of my filesystem (encrypted ext4 /home)?
While using gThumb to browse pictures my hard drive went busy and everything froze (system became totally unresponsive) for a couple of minutes.
dmesg showed the similar errors as reported here:

[ 2836.262337] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
[36400.261956] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
[36400.650623] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
[36402.062655] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.