All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2: cursor started to disappear
Date: Mon, 28 Jul 2003 13:34:31 -0700	[thread overview]
Message-ID: <20030728133431.0a4825ca.akpm@osdl.org> (raw)
In-Reply-To: <20030728203838.GB1815@win.tue.nl>

Andries Brouwer <aebr@win.tue.nl> wrote:
>
> On Mon, Jul 28, 2003 at 01:17:41PM -0700, Andrew Morton wrote:
> > Andries Brouwer <aebr@win.tue.nl> wrote:
> > >
> > > On Mon, Jul 28, 2003 at 08:14:08PM +0200, Pavel Machek wrote:
> > > 
> > > > Plus I'm seeing some silent data corruption. It may be
> > > > swsusp or loop related
> > > 
> > > Loop is not stable at all. Unsuitable for daily use.
> > 
> > That's the first I've heard about it.  Do you have some details on this?  A
> > test case perhaps?
> 
> Yes, there are many reports, and it is easy to confirm.
> 
> By some coincidence just a moment ago we saw the announcement of
> Bugzilla bug 1000:
> 
> [Bug 1000] New: file corruption using cryptoloop on ext2/ext3

That's cryptoloop.  I thought you were referring to vanilla loop.

Are you saying that the problems are only with cryptoloop, or does normal
old loop have some bug?


  reply	other threads:[~2003-07-28 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 18:14 2.6.0-test2: cursor started to disappear Pavel Machek
2003-07-28 18:27 ` Andries Brouwer
2003-07-28 18:34   ` Pavel Machek
2003-07-28 19:00     ` Andries Brouwer
2003-07-28 19:18       ` Pavel Machek
2003-07-29 17:20     ` Mikulas Patocka
2003-07-28 20:17   ` Andrew Morton
2003-07-28 20:38     ` Andries Brouwer
2003-07-28 20:34       ` Andrew Morton [this message]
2003-07-28 23:01         ` Andries Brouwer
2003-07-29  9:44     ` Pavel Machek

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=20030728133431.0a4825ca.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.