mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sidik Isani <isani@cfht.hawaii.edu>
To: linux-kernel@vger.kernel.org
Subject: CRAMFS error "attempt to access beyond end of device"
Date: Fri, 29 Jun 2001 13:50:04 -1000 (HST)	[thread overview]
Message-ID: <200106292350.NAA08050@otto.cfht.hawaii.edu> (raw)

Hello -

  Is there maybe a missing boundary check in cramfs that causes
  accesses slightly past (up to 24 or 32K?) the end of a device?
  Here's an example of a cramfs image mounted on a loop device
  (the same thing happens with other block devices, and when the
  kernel itself mounts a partition as cramfs-root.)

attempt to access beyond end of device
07:01: rw=0, want=1156, limit=1152
attempt to access beyond end of device
07:01: rw=0, want=1160, limit=1152
attempt to access beyond end of device
07:01: rw=0, want=1164, limit=1152

  The messages appear while running "diff -r" against the original tree.
  The diff itself doesn't find any problems with the filesystem.
  The size of the cramfs is 1179648 bytes, or exactly 1152 * 1024.
  My kernel version is 2.4.5, but this behavior has existed since
  the 2.4.0-test kernels.

  If anyone has ideas on this, please let me know.

- Sidik

                 reply	other threads:[~2001-06-29 23:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200106292350.NAA08050@otto.cfht.hawaii.edu \
    --to=isani@cfht.hawaii.edu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®