public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Rick Bronson <rick@efn.org>
To: dedekind@yandex.ru
Cc: linux-mtd@lists.infradead.org
Subject: Re: infinite loop in jffs2_flush_wbuf_gc()?
Date: Fri, 08 Jul 2005 09:59:12 -0700	[thread overview]
Message-ID: <E1DqwC0-0002Er-00@amazonia.client.comcast.net> (raw)
In-Reply-To: <42CEAA83.20908@yandex.ru> (dedekind@yandex.ru)

Dear Artem,

  Thanks very much for the response.

  Sorry, I never got your previous email answering my original post.
Nor did I see it in my saved archive of the mtd mailing list.  Hmmm.

  Anyway, I got the latest CVS a few weeks ago but then had to do:

cvs update -dP -D 2005-03-04

  because I'm using 2.4.27 on a ARM.

  I noticed that the code in wbuf.c is pretty much the same in the
latest CVS as in the 2005-03-04 version so I thought someone might
have stumbled upon this issue.

> you didn't write the version of Linux/MTD you're using. It's important 
> because I fixed one endless GC thread loop problem recently. Please, try 
> a fresh MTD snapshot (download it from CVS). If it won't help - come back.

  Maybe you could tell me roughly the fix, I'd really appreciate that.

  Thanks again.

  Rick
  

> Rick Bronson wrote:
> > Hi,
> > 
> >   I seem to encounter an infinite loop in in jffs2_flush_wbuf_gc() in
> > wbuf.c starting at: 
> > 
> Rick,
> 
> this is the second time you're reporting this and this is the second 
> time I inquire the version of your MTD :-) Is it the last MTD?
> 
> http://lists.infradead.org/pipermail/linux-mtd/2005-July/012948.html
> 
> -- 
> Best Regards,
> Artem B. Bityuckiy,
> St.-Petersburg, Russia.
> 

  reply	other threads:[~2005-07-08 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 16:26 infinite loop in jffs2_flush_wbuf_gc()? Rick Bronson
2005-07-08 16:32 ` Artem B. Bityuckiy
2005-07-08 16:59   ` Rick Bronson [this message]
2005-07-11 14:55 ` David Woodhouse
     [not found]   ` <E1Ds2ma-0005ta-00@amazonia.client.comcast.net>
     [not found]     ` <1121108481.27264.129.camel@hades.cambridge.redhat.com>
     [not found]       ` <E1Ds4AF-00063d-00@amazonia.client.comcast.net>
     [not found]         ` <1121115438.3430.6.camel@localhost.localdomain>
     [not found]           ` <E1DsMIp-0004U9-00@amazonia.client.comcast.net>
     [not found]             ` <1121181101.12169.4.camel@hades.cambridge.redhat.com>
     [not found]               ` <E1DsNHk-0004bq-00@amazonia.client.comcast.net>
     [not found]                 ` <1121186381.12086.6.camel@localhost.localdomain>
     [not found]                   ` <E1DsOD0-0004iT-00@amazonia.client.comcast.net>
     [not found]                     ` <1121189272.12224.10.camel@localhost.localdomain>
     [not found]                       ` <E1Dspqm-0003zl-00@amazonia.client.comcast.net>
     [not found]                         ` <1121294622.12224.87.camel@localhost.localdomain>
2005-07-14 14:11                           ` Rick Bronson
2005-07-14 14:39                             ` David Woodhouse
2005-07-14 17:14                             ` Artem B. Bityuckiy
2005-07-14 17:18                             ` Artem B. Bityuckiy

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=E1DqwC0-0002Er-00@amazonia.client.comcast.net \
    --to=rick@efn.org \
    --cc=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.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