Re: v2.6.24-rc2-409-g9418d5d: attempt to access beyond end of device

[Ingo Molnar <mingo@elte.hu>]

(added Cc:s)

* Thomas Meyer <thomas@m3y3r.de> wrote:

> Thomas Meyer schrieb:
> > i get these errors in the kernel log while trying to copy a file from an
> > iso9660 file system (/dev/sr0) to my intenal hard disk. This is the
> > second cd/dvd that gives me this error. kernel 2.6.23 works without any
> > problems, so i think this is not an medium error:
> >
> > ISO 9660 Extensions: Microsoft Joliet Level 3
> > ISOFS: changing to secondary root
> > attempt to access beyond end of device
> > sr0: rw=0, want=81220, limit=40944
> > Buffer I/O error on device sr0, logical block 20304
> > attempt to access beyond end of device
> > sr0: rw=0, want=81224, limit=40944
> > Buffer I/O error on device sr0, logical block 20305
> > attempt to access beyond end of device
> > sr0: rw=0, want=81228, limit=40944
> > Buffer I/O error on device sr0, logical block 20306
> > attempt to access beyond end of device
> > sr0: rw=0, want=81232, limit=40944
> > Buffer I/O error on device sr0, logical block 20307
> > attempt to access beyond end of device
> > sr0: rw=0, want=81236, limit=40944
> > Buffer I/O error on device sr0, logical block 20308
> > attempt to access beyond end of device
> > sr0: rw=0, want=81240, limit=40944
> > Buffer I/O error on device sr0, logical block 20309
> > attempt to access beyond end of device
> > sr0: rw=0, want=81244, limit=40944
> > Buffer I/O error on device sr0, logical block 20310
> > attempt to access beyond end of device
> > sr0: rw=0, want=81248, limit=40944
> > Buffer I/O error on device sr0, logical block 20311
> > attempt to access beyond end of device
> > sr0: rw=0, want=81220, limit=40944
> > Buffer I/O error on device sr0, logical block 20304
> > attempt to access beyond end of device
> > sr0: rw=0, want=81224, limit=40944
> > Buffer I/O error on device sr0, logical block 20305
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028968, limit=40944
> > Buffer I/O error on device sr0, logical block 257241
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028972, limit=40944
> > Buffer I/O error on device sr0, logical block 257242
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028976, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028980, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028984, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028988, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028992, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028996, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028968, limit=40944
> > attempt to access beyond end of device
> > sr0: rw=0, want=1028972, limit=40944
> >
> > does anybody have similiar problems with current linus kernel?
> >   
>
> I have a question: How to find out between which two tags a given 
> commit lies?
> 
> E.g. commit 6f5391c283d7fdcf24bf40786ea79061919d1e1d ([SCSI] Get rid 
> of scsi_cmnd->done), which is the last commit that changed 
> drivers/scsi/sr.c

good question. A quirky way would be to look at:

  ls -l .git/refs/tags/

and compare it with the commit date. But ... that doesnt necessarily 
work if a tag has been created after the commit but before the commit 
was merged upstream.

> i now discovered (using gitk and a lot of scolling) that above commit 
> is after v2.6.23 but before v2.6.24-rc1 (so it is a possible offender)
> 
> You see i am just too lazy to bisect (and reboot 20th times or so) and 
> i just wanted to try my luck and revert the last
>  commit and see if this fixes my problem.
> 
> By the way: Reverting commit 6f5391c283d7fdcf24bf40786ea79061919d1e1d 
> makes the same cd medium readable again on v2.6.24-rc2-409-g9418d5d.

nice - that commit should then be reverted.

	Ingo