All of lore.kernel.org
 help / color / mirror / Atom feed
From: ch@murgatroid.com (Christopher Hoover)
To: linux-mtd@lists.infradead.org
Subject: Another mmap / jffs2 problem (was RE: 2.5.59-rmk1: unmap_vmas: VMA list is not sorted correctly!)
Date: Thu, 6 Mar 2003 14:47:35 -0800	[thread overview]
Message-ID: <002001c2e432$61b33f30$e55f040f@bergamot> (raw)
In-Reply-To: <000d01c2e2ba$95246520$7a00000a@bergamot>

> I'm getting "unmap_vmas: VMA list is not sorted
> correctly!" with 2.5.59-rmk1 on a badgepad4 
> (SA-1110).  I take it that this is bad.  :-)

I tracked this down to the use of mmap within pppd
(ppp-2.4.1/pppd/tdb.c) on a file in jffs2.  That last part -*- the
mmap'ed file is in jffs2 -*- is key.

I don't always get the "VMA list is not sorted message", but pppd always
segfaults when it starts mucking with the mmap'ed file data.

If I place the file in /tmp, which is a ramfs file system in my setup,
pppd behaves.

Here's the segfault:

pppd-with-mmap: unhandled page fault at 0x000001e3, code 0xc334f007
pgd = c334c000
[000001e3] *pgd=c238b011, *pte=00000000, *ppte=00000000
pc : [<40057f7c>]    lr : [<00026ad4>]    Not tainted
sp : befffd14  ip : befffd28  fp : 00000000
r10: 933f4b6e  r9 : 00000007  r8 : 000438c8
r7 : befffd28  r6 : 0004df80  r5 : 00000004  r4 : 000001e4
r3 : ffffffff  r2 : 00000004  r1 : 000001e3  r0 : befffd28
Flags: nzCv  IRQs on  FIQs on  Mode USER_32  Segment user
Control: C334F17F  Table: C334F17F  DAC: 00000015



Details: 2.5.59-rmk1, uClibc-0.9.19, ppp-2.4.1, gcc-3.2.2

-ch
mailto:ch-at-murgatroid.com

       reply	other threads:[~2003-03-06 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000d01c2e2ba$95246520$7a00000a@bergamot>
2003-03-06 22:47 ` Christopher Hoover [this message]
2003-03-06 23:28   ` Another mmap / jffs2 problem (was RE: 2.5.59-rmk1: unmap_vmas: VMA list is not sorted correctly!) Russell King - ARM Linux
2003-03-07  1:30     ` Christopher Hoover
2003-03-07  2:10       ` Christopher Hoover
2003-03-07  6:53       ` David Woodhouse

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='002001c2e432$61b33f30$e55f040f@bergamot' \
    --to=ch@murgatroid.com \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.