public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	linux-scsi@vger.kernel.org,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Maarten Bressers <mbres@gentoo.org>,
	Daniel Drake <dsd@gentoo.org>,
	Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>
Subject: Re: [Cbe-oss-dev] [regression/bisected] corrupt CD data after media change and delay
Date: Sun, 13 Jul 2008 08:33:51 -0500	[thread overview]
Message-ID: <1215956031.4326.4.camel@localhost.localdomain> (raw)
In-Reply-To: <5a4c581d0807120508m758df950i76fabdb70dfa2d07@mail.gmail.com>

On Sat, 2008-07-12 at 14:08 +0200, Alessandro Suardi wrote:
> On Fri, Jul 11, 2008 at 11:25 PM, Alessandro Suardi
> sr0: rw=0, want=3291928, limit=2097151
> [asuardi@sandman sdlmame0126]$ h | grep siz
>   958  cat /sys/block/sr0/size
>  1031  h | grep siz
> [asuardi@sandman sdlmame0126]$ !958
> cat /sys/block/sr0/size
> 6993536
> 
> <eject, remount DVD>
> 
> [asuardi@sandman sdlmame0126]$ !mount
> mount -r /cdrom
> [asuardi@sandman sdlmame0126]$ cat /sys/block/sr0/size
> 6993536
> 
> <now everything works fine>
> 
> Possibly a new bug then - since size is always the same ?

It looks like a re-manifestation of Geert's bug.

You said everything worked in -rc7, and there actually have been no sr
changes at all between then and now, so I'm a bit confused as to how it
could reappear.  Could you try a bisection search for it (first
re-verify -rc7 is OK, just in case that's a false negative).

Thanks,

James



  reply	other threads:[~2008-07-13 13:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 14:06 [regression/bisected] corrupt CD data after media change and delay Geert Uytterhoeven
2008-06-06 15:13 ` James Bottomley
2008-06-06 17:27   ` Geert Uytterhoeven
2008-06-09 12:54   ` Geert Uytterhoeven
2008-06-09 13:54     ` [Cbe-oss-dev] " Geert Uytterhoeven
2008-06-09 15:05       ` James Bottomley
2008-06-09 15:27         ` Geert Uytterhoeven
     [not found]           ` <1213028647.3508.33.camel@localhost.localdomain>
2008-06-10 15:11             ` Geert Uytterhoeven
2008-06-10 15:22               ` James Bottomley
2008-06-10 15:20           ` James Bottomley
2008-06-10 15:49             ` Boaz Harrosh
2008-06-10 15:56               ` James Bottomley
2008-06-10 16:12                 ` Boaz Harrosh
2008-06-10 16:17                   ` James Bottomley
2008-06-13 17:33 ` Geert Uytterhoeven
2008-06-18  8:47   ` Alessandro Suardi
2008-06-18 11:13     ` Geert Uytterhoeven
2008-06-18 12:15       ` Alessandro Suardi
2008-06-21 14:18         ` Alessandro Suardi
2008-06-22  8:18           ` Geert Uytterhoeven
2008-06-22 13:14             ` Alessandro Suardi
2008-07-11 21:25               ` Alessandro Suardi
2008-07-12 12:08                 ` Alessandro Suardi
2008-07-13 13:33                   ` James Bottomley [this message]
2008-07-23 20:25                     ` Alessandro Suardi

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=1215956031.4326.4.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=alessandro.suardi@gmail.com \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mbres@gentoo.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