public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christophe Broult <cbroult@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [2.4.0-test11 BUG] kernel: _isofs_bmap: block >= EOF (559939584, 4096)
Date: 22 Nov 2000 14:37:25 +0100	[thread overview]
Message-ID: <87em04ku0a.fsf@valiosys.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]


With 2.4.0-test11, I am unable to access to the content of CDROMs. For example:

  root@madison:~# mount /cdrom/ ; df ;ls -la /cdrom ; umount /cdrom/
  Filesystem           1k-blocks      Used Available Use% Mounted on
  /dev/scsi/host0/bus0/target0/lun0/part2
                         1014990    893570     68975  93% /
  /dev/scsi/host0/bus0/target0/lun0/part1
                          508647    363802    118571  76% /usr/share
  /dev/scsi/host0/bus0/target0/lun0/part4
                          494423    437471     31415  94% /home
  /dev/scsi/host0/bus0/target3/lun0/cd
                          658882    658882         0 100% /cdrom
  total 0
  root@madison:~# 

and the following lines show up in a xconsole window:

  Nov 22 14:08:30 localhost kernel: VFS: Disk change detected on device sr(11,0)
  Nov 22 14:08:30 localhost kernel: ISO 9660 Extensions: Microsoft Joliet Level 1
  Nov 22 14:08:31 localhost kernel: ISO 9660 Extensions: RRIP_1991A
  Nov 22 14:08:31 localhost kernel: _isofs_bmap: block >= EOF (559939584, 4096)

I have just verified that this problem did not occur with
2.4.0-test10. 

Chris

-- 
"Man is distinguished from all other creatures by
the faculty of laughter."
- Joseph Addison

[-- Attachment #2: ver.txt --]
[-- Type: text/plain, Size: 761 bytes --]

-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux madison 2.4.0-test11 #1 Mon Nov 20 12:46:56 CET 2000 i586 unknown
Kernel modules         2.3.20
Gnu C                  2.95.2
Gnu Make               3.79.1
Binutils               2.10.91
Linux C Library        > libc.2.2
Dynamic linker         ldd (GNU libc) 2.2
Procps                 2.0.6
Mount                  2.10o
Net-tools              2.05
Console-tools          0.2.3
Sh-utils               2.0
Modules Loaded         ipv6 af_packet ipt_state ipt_REJECT ipt_LOG ipt_limit parport_pc lp ip_conntrack_ftp parport iptable_nat ip_conntrack iptable_filter ip_tables gus ad1848 sound soundcore quickcam videodev usb-ohci usbcore binfmt_misc

                 reply	other threads:[~2000-11-22 14:49 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=87em04ku0a.fsf@valiosys.com \
    --to=cbroult@yahoo.com \
    --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