public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Edward Shishkin <edward@namesys.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/3] reiser4 fixups
Date: Tue, 17 Jul 2007 10:24:16 -0600	[thread overview]
Message-ID: <1184689456.457333.3.camel@localhost> (raw)
In-Reply-To: <469BBE07.2010606@namesys.com>


[-- Attachment #1.1: Type: text/plain, Size: 631 bytes --]

On Mon, 2007-07-16 at 22:50 +0400, Edward Shishkin wrote:
> Zan Lynx wrote:
> ...
> 
> >Unable to handle kernel NULL pointer dereference at 0000000000000000
> RIP: 
> > [<ffffffff8033d324>] reiser4_tree_by_page+0x4/0x20
[snip]
> This is bug in Zam's new file_read: unlocked page was reclaimed,
> then reiser4_tree_by_page() looks at page->mapping->host.
> The patch #3 fixes this problem.
> 
> Andrew, please apply the following series.

These three patches appear to have fixed my problem.  I ran it all of
last afternoon and last night, and it did not oops.

Thank you, Edward.

-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3137 bytes --]

      reply	other threads:[~2007-07-17 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 18:03 2.6.22-rc6-mm1 reiser4_tree_by_page NULL pointer Zan Lynx
2007-07-11 18:39 ` Edward Shishkin
2007-07-12 20:31   ` Zan Lynx
2007-07-13 16:41     ` Zan Lynx
2007-07-16 18:50       ` [patch 0/3] reiser4 fixups Edward Shishkin
2007-07-17 16:24         ` Zan Lynx [this message]

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=1184689456.457333.3.camel@localhost \
    --to=zlynx@acm.org \
    --cc=akpm@linux-foundation.org \
    --cc=edward@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@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