public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Kyungmin Park <kyungmin.park@samsung.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] MTD: OneNAND: fix numerous races
Date: Fri, 21 Sep 2007 16:56:02 +0300	[thread overview]
Message-ID: <1190382963.14370.209.camel@sauron> (raw)
In-Reply-To: <1190382415.14370.207.camel@sauron>

On Fri, 2007-09-21 at 16:46 +0300, Artem Bityutskiy wrote:
> >From 5383a93bc534aa15c4e2a260fe5ca4a4ecb8310e Mon Sep 17 00:00:00 2001
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Date: Fri, 21 Sep 2007 15:34:43 +0300
> Subject: [PATCH] MTD: OneNAND: fix numerous races
> 
> This patch make the OneNAND driver much less racy. It fixes
> our "onenand_wait: read timeout!" heisenbugs. The reason of
> these bugs was that the driver did not lock the chip when
> accessing OTP, and it screwed up OneNAND state when the OTP
> was read while JFFS2 was doing FS checking.
> 
> This patch also fixes other races I spotted:
> 1. BBT was not protected
> 2. Access to ecc_stats was not protected
> 
> Now the chip is locked when BBT is accessed.
> 
> To fix all of these I basically split all interface functions
> on 'function()' and 'function_nolock()' parts.
> 
> This was tested on N800 hardware.
> 
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>

Sorry, this patch was against a little older kernel. But anyways,
I'd like to get feedback from Kyungmin.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2007-09-21 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 13:46 [PATCH] MTD: OneNAND: fix numerous races Artem Bityutskiy
2007-09-21 13:56 ` Artem Bityutskiy [this message]
2007-09-21 15:30 ` [PATCH try 2] " Artem Bityutskiy
2007-09-26 23:50   ` Kyungmin Park
2007-09-27  8:55     ` Artem Bityutskiy

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=1190382963.14370.209.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --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