public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: problems with JFFS2 assert failure on mutex
Date: Tue, 20 Jul 2004 09:41:32 -0400	[thread overview]
Message-ID: <1090330892.4614.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1090250271.14173.6.camel@famine>

On Mon, 2004-07-19 at 17:17 +0200, Øyvind Harboe wrote:
> I was working on a different problem when I came across a mutex that
> was being obtained twice(discovered via eCos asserts).
> 
> On the surface of it, this patch looks correct.

Looks correct; I've committed an equivalent to CVS. Thanks.

> Comments?

Only that this error path should never happen. The call to
jffs2_gc_fetch_inode() for a valid inode should _never_ fail.

-- 
dwmw2

  reply	other threads:[~2004-07-20 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 15:17 problems with JFFS2 assert failure on mutex Øyvind Harboe
2004-07-20 13:41 ` David Woodhouse [this message]
2004-07-20 15:27   ` Øyvind Harboe

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=1090330892.4614.1.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=oyvind.harboe@zylin.com \
    /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