From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org
Subject: RAMFS
Date: Fri, 2 Feb 2001 15:51:53 +0000 (GMT) [thread overview]
Message-ID: <E14OiV8-0006hH-00@the-village.bc.nu> (raw)
Random quick poking
Does this fix the ramfs problem in -ac ?
--- fs/ramfs/inode.c~ Wed Jan 31 22:02:16 2001
+++ fs/ramfs/inode.c Fri Feb 2 14:51:47 2001
@@ -174,7 +174,6 @@
inode->i_blocks += IBLOCKS_PER_PAGE;
rsb->free_pages--;
SetPageDirty(page);
- UnlockPage(page);
} else {
ClearPageUptodate(page);
ret = 0;
@@ -264,6 +263,7 @@
if (! ramfs_alloc_page(inode, page))
return -ENOSPC;
+ UnlockPage(page);
return 0;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-02 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 15:51 Alan Cox [this message]
2001-02-02 17:57 ` RAMFS Ingo Oeser
2001-02-02 19:24 ` RAMFS Mike Galbraith
2001-02-02 20:41 ` RAMFS Ingo Oeser
2001-02-02 21:03 ` RAMFS Mike Galbraith
2001-02-03 7:13 ` RAMFS Mike Galbraith
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=E14OiV8-0006hH-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).