From: Seth Forshee <seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Matt Fleming <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"H. Peter Anvin" <hpa-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: Problem mounting efivarfs in 3.9
Date: Thu, 7 Mar 2013 09:09:41 -0600 [thread overview]
Message-ID: <20130307150941.GB24233@thinkpad-t410> (raw)
In-Reply-To: <1362668558.15011.203.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Thu, Mar 07, 2013 at 03:02:38PM +0000, Matt Fleming wrote:
> On Thu, 2013-03-07 at 08:56 -0600, Seth Forshee wrote:
> > 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.
>
> A patch to allow pstore names is in the pull request I sent to Peter and
> Ingo yesterday,
>
> http://marc.info/?l=linux-kernel&m=136258373231608&w=2
Great. Thanks!
Seth
prev parent reply other threads:[~2013-03-07 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 14:56 Problem mounting efivarfs in 3.9 Seth Forshee
2013-03-07 15:00 ` shea-yfkUTty7RcRWk0Htik3J/w
2013-03-07 15:02 ` Matt Fleming
[not found] ` <1362668558.15011.203.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-03-07 15:09 ` Seth Forshee [this message]
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=20130307150941.GB24233@thinkpad-t410 \
--to=seth.forshee-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=hpa-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.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