public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Tassonis <stuff@decentral.ch>
To: Richard Weinberger <richard.weinberger@gmail.com>,
	linux-kernel@vger.kernel.org, xerofoify@gmail.com
Subject: Re: [BUG] Kernel Panic in squashfs
Date: Fri, 06 Feb 2015 20:56:09 +0100	[thread overview]
Message-ID: <54D51C59.2080208@decentral.ch> (raw)

> On Fri, Feb 6, 2015 at 5:55 PM, Tim Tassonis <stuff@decentral.ch> wrote:
>> Hi all
>>
>>
>> Just found out that squashfs panics when compiled in statically instead of
>> as a module, when mounting an sqf file. The sequence I did was:
>>
>>
>> # mkdir /mnt/gaia-ro
>>
>> # mount /gaiarule.sqf  /mnt/gaia-ro -t squashfs -o loop
>>
>> Maybe it is of importance that the sqf file is located in the initramfs. The
>> kernel was panicking reliably with different sqf files, on different
>> hardware upon the mount command, with "unable to handle kernel paging
>> request". This was on 3.18.5. As soon as I compiled squashfs as a modules,
>> the problem went away.
>>
>> If you need further details, please cc me directly, as I unsubscribed from
>> the list due to not being able to handle the massive load.
>
> What about sharing the actual kernel panic? :-)

Well, I was trying to reproduce it. Upgraded to 3.18.6, built the kernel 
with static squashfs, and now it doesn't panic anymore.

Guess some fixes for 3.18.6 fixed this too. If somebody really, really 
cares, I could go through the whole procedure again with 3.18.6, but I 
guess, as it's gone now, this would be rather academeic.

Bye
Tim


             reply	other threads:[~2015-02-06 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 19:56 Tim Tassonis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-06 18:47 [BUG] Kernel Panic in squashfs Tim Tassonis
2015-02-06 16:55 Tim Tassonis
2015-02-06 17:37 ` Richard Weinberger

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=54D51C59.2080208@decentral.ch \
    --to=stuff@decentral.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=xerofoify@gmail.com \
    /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