All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Ungerer <gerg@snapgear.com>,
	linux-kernel@vger.kernel.org,
	David McCullough <davidm@snapgear.com>
Subject: Re: [PATCH]: uClinux (MMU-less) patches against 2.5.28
Date: Fri, 26 Jul 2002 17:01:05 +0100	[thread overview]
Message-ID: <6881.1027699265@redhat.com> (raw)
In-Reply-To: <1027703485.13429.53.camel@irongate.swansea.linux.org.uk>


alan@lxorguk.ukuu.org.uk said:
>  Well for a starter lets try user writing a block to flash which needs
> an erase from a block which happens to be not yet paged in and so
> still on the flash you are writing to.

What locks the page? Surely our write() implementation is just using 
copy_from_user(), to get the data from the user, and each erase and write 
to the flash chip can be considered atomic -- what's holding a lock, and 
what's causing the deadlock?

--
dwmw2



  reply	other threads:[~2002-07-26 15:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  6:56 [PATCH]: uClinux (MMU-less) patches against 2.5.28 Greg Ungerer
2002-07-25 14:52 ` David Woodhouse
2002-07-26  0:08   ` Greg Ungerer
2002-07-26  1:20   ` Greg Ungerer
2002-07-26  8:19     ` David Woodhouse
2002-07-26 10:39       ` Alan Cox
2002-07-26  9:39         ` David Woodhouse
2002-07-26 10:56           ` Alan Cox
2002-07-26  9:58             ` David Woodhouse
2002-07-26 14:50               ` Alan Cox
2002-07-26 14:03                 ` David Woodhouse
2002-07-26 17:11                   ` Alan Cox
2002-07-26 16:01                     ` David Woodhouse [this message]
2002-07-26 17:27                       ` Alan Cox
2002-07-26 16:27                         ` David Woodhouse
2002-07-26 15:08       ` gerg
2002-07-26 15:45         ` David Woodhouse

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=6881.1027699265@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidm@snapgear.com \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.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 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.