From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] linux-2.6.24: avoid kernel error if ubifs superblock read fails
Date: Mon, 27 Sep 2010 13:15:14 -0700 [thread overview]
Message-ID: <4CA0FB52.4090000@mentor.com> (raw)
In-Reply-To: <4CA059F2.5090509@dresearch.de>
Steffen Sledz wrote:
> Am 27.09.2010 09:40, schrieb Frans Meulenbroeks:
>>>> * .get_sb is called on mounts with automatic fs detection too, so this
>>>> function should not print an error if it cannot read the superblock
>>>> (new behaviour conforms the other fs types)
>>>> ...
>> Hm, I have some concerns:
>>
>> the first concern is that mainline 2.6.34 still has the code you have deleted.
>> I'd expect that others would have bumped into this too and that it
>> would have been fixed this upstream.
>> Since it isn't, chances are that upstream might have fixed the autofs
>> detection in a different way. If they do this differently maybe we
>> should backport that solution.
>
> I've suggested the same patch at the LKML and informed the UBIFS authors. But i do believe because of it's "low prio" it will need some time to go into the mainline.
So it is queued somewhere then?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-27 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 8:33 [PATCH] linux-2.6.24: avoid kernel error if ubifs superblock read fails Steffen Sledz
2010-09-27 7:18 ` Steffen Sledz
2010-09-27 7:40 ` Frans Meulenbroeks
2010-09-27 8:46 ` Steffen Sledz
2010-09-27 20:15 ` Tom Rini [this message]
2010-09-28 6:10 ` Steffen Sledz
2010-09-28 8:33 ` Steffen Sledz
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=4CA0FB52.4090000@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.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