I noticed a similar problem on one of my machines, which is introduced by:
commit 47f531e8ba3bc3901a0c493f4252826c41dea1a1
Author: Matt Fleming <email address hidden>
Date: Thu Jan 31 19:02:03 2013 +0000
efivarfs: Validate filenames much more aggressively
Joe, you might just want to try reverting this commit to see if it fixes the issue. You'll also need to revert the following, which depends on that commit:
commit da27a24383b2b10bf6ebd0db29b325548aafecb4
Author: Matt Fleming <email address hidden>
Date: Fri Feb 1 11:02:28 2013 +0000
efivarfs: guid part of filenames are case-insensitive
(Note that the SHA-1's here are different than the ones in the raring repository)
I noticed a similar problem on one of my machines, which is introduced by:
commit 47f531e8ba3bc39 01a0c493f425282 6c41dea1a1
Author: Matt Fleming <email address hidden>
Date: Thu Jan 31 19:02:03 2013 +0000
efivarfs: Validate filenames much more aggressively
Joe, you might just want to try reverting this commit to see if it fixes the issue. You'll also need to revert the following, which depends on that commit:
commit da27a24383b2b10 bf6ebd0db29b325 548aafecb4
Author: Matt Fleming <email address hidden>
Date: Fri Feb 1 11:02:28 2013 +0000
efivarfs: guid part of filenames are case-insensitive
(Note that the SHA-1's here are different than the ones in the raring repository)