From: Seth Forshee <seth.forshee@canonical.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
stable@vger.kernel.org
Subject: Problem mounting efivarfs in 3.9
Date: Thu, 7 Mar 2013 08:56:01 -0600 [thread overview]
Message-ID: <20130307145601.GA24233@thinkpad-t410> (raw)
Hi Matt,
I found myself unable to mount efivarfs on one of my machines in 3.9.
This is due to your patch to be more aggressive about validating
filenames. This machine had some crash dumps from pstore, which start
with "dump-type". However now efivars expects the guid to follow the
first '-' character, despite the fact that the efivars pstore code is
creating the file names starting with dump-type. Since these names fail
the validation the mount fails.
These changes are now in some of the stable releases as well (3.8.x at
minumum).
Thanks,
Seth
next reply other threads:[~2013-03-07 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 14:56 Seth Forshee [this message]
2013-03-07 15:00 ` Problem mounting efivarfs in 3.9 shea
2013-03-07 15:02 ` Matt Fleming
2013-03-07 15:09 ` Seth Forshee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130307145601.GA24233@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox