From: Edward Shishkin <edward.shishkin@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [patch 1/7] roll back reiser4-fixed-null-pointer-dereference.patch
Date: Tue, 2 Feb 2010 16:24:45 +0100 [thread overview]
Message-ID: <201002021624.45767.edward.shishkin@gmail.com> (raw)
Roll back reiser4-fixed-null-pointer-dereference.patch
(wrong stuff)
Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
fs/reiser4/super_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.33-rc5-mm1/fs/reiser4/super_ops.c
===================================================================
--- linux-2.6.33-rc5-mm1.orig/fs/reiser4/super_ops.c
+++ linux-2.6.33-rc5-mm1/fs/reiser4/super_ops.c
@@ -395,7 +395,7 @@ static void reiser4_sync_inodes(struct s
reiser4_context *ctx;
long to_write;
- if (wbc == NULL || wbc->for_kupdate)
+ if (wbc->for_kupdate)
/* reiser4 has its own means of periodical write-out */
return;
reply other threads:[~2010-02-02 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201002021624.45767.edward.shishkin@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).