From: "Carlos E. Gorges" <carlos@techlinux.com.br>
To: linux-kernel@vger.kernel.org
Subject: Re: Possible patch for reiserfs-3.6.22 against 2.4.0-test12
Date: Wed, 13 Dec 2000 11:14:30 -0200 [thread overview]
Message-ID: <00121311262200.00911@shark.techlinux> (raw)
In-Reply-To: <873dftywn6.fsf@cartman.azz.net>
In-Reply-To: <873dftywn6.fsf@cartman.azz.net>
> Hiya.
>
> The latest reiserfs patch on ftp.namesys.com causes compilation errors
> against test12 due to the task queue changes. Does this look correct?
>
Please, somebody can test this patch
-- BOF --
diff -ur linux-bk/fs/reiserfs/journal.c linux/fs/reiserfs/journal.c
--- linux-bk/fs/reiserfs/journal.c Tue Dec 12 14:38:22 2000
+++ linux/fs/reiserfs/journal.c Tue Dec 12 17:41:19 2000
@@ -77,7 +77,9 @@
/* wait on this if you need to be sure you task queue entries have been run */
static DECLARE_WAIT_QUEUE_HEAD(reiserfs_commit_thread_done) ;
-DECLARE_TASK_QUEUE(reiserfs_commit_thread_tq) ;
+
+/*DECLARE_TASK_QUEUE(reiserfs_commit_thread_tq) ; */
+task_queue *reiserfs_commit_thread_tq = NULL;
#define JOURNAL_TRANS_HALF 1018 /* must be correct to keep the desc and commit structs at 4k */
@@ -1762,7 +1764,7 @@
ct->p_s_sb = p_s_sb ;
ct->jindex = jindex ;
ct->task_done = NULL ;
- ct->task.next = NULL ;
+ INIT_LIST_HEAD(&ct->task.list);
ct->task.sync = 0 ;
ct->task.routine = (void *)(void *)reiserfs_journal_commit_task_func ;
ct->self = ct ;
@@ -1777,7 +1779,7 @@
ct = kmalloc(sizeof(struct reiserfs_journal_commit_task), GFP_BUFFER) ;
if (ct) {
setup_commit_task_arg(ct, p_s_sb, jindex) ;
- queue_task(&(ct->task), &reiserfs_commit_thread_tq);
+ queue_task(&(ct->task), reiserfs_commit_thread_tq);
wake_up(&reiserfs_commit_thread_wait) ;
} else {
#ifdef CONFIG_REISERFS_CHECK
@@ -1813,13 +1814,13 @@
lock_kernel() ;
while(1) {
- while(reiserfs_commit_thread_tq) {
- run_task_queue(&reiserfs_commit_thread_tq) ;
+ while(reiserfs_commit_thread_tq) {
+ run_task_queue(reiserfs_commit_thread_tq) ;
}
/* if there aren't any more filesystems left, break */
if (reiserfs_mounted_fs_count <= 0) {
- run_task_queue(&reiserfs_commit_thread_tq) ;
+ run_task_queue(reiserfs_commit_thread_tq) ;
break ;
}
wake_up(&reiserfs_commit_thread_done) ;
diff -ur linux-bk/include/linux/reiserfs_fs.h linux/include/linux/reiserfs_fs.h
--- linux-bk/include/linux/reiserfs_fs.h Tue Dec 12 14:39:34 2000
+++ linux/include/linux/reiserfs_fs.h Tue Dec 12 17:31:09 2000
@@ -1565,8 +1565,8 @@
int do_not_lock ;
} ;
-extern task_queue reiserfs_commit_thread_tq ;
-extern task_queue reiserfs_end_io_tq ;
+extern task_queue *reiserfs_commit_thread_tq ;
+extern task_queue *reiserfs_end_io_tq ;
extern wait_queue_head_t reiserfs_commit_thread_wait ;
/* biggest tunable defines are right here */
-- EOF --
cya;
--
_________________________
Carlos E Gorges
(carlos@techlinux.com.br)
Tech informática LTDA
Brazil
_________________________
-
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 prev parent reply other threads:[~2000-12-13 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 0:47 Possible patch for reiserfs-3.6.22 against 2.4.0-test12 Adam Sampson
2000-12-13 13:14 ` Carlos E. Gorges [this message]
2000-12-13 15:08 ` Jorge Boncompte (DTI2)
-- strict thread matches above, loose matches on Subject: below --
2000-12-13 1:18 Steven Cole
2000-12-13 1:22 ` Adam Sampson
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=00121311262200.00911@shark.techlinux \
--to=carlos@techlinux.com.br \
--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.