From: Chris Mason <chris.mason@oracle.com>
To: David Sterba <dave@jikos.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
bugzilla-daemon <bugzilla-daemon@bugzilla.kernel.org>,
bugme-daemon <bugme-daemon@bugzilla.kernel.org>,
fox <fox@murder.cz>
Subject: Re: [Bugme-new] [Bug 29302] New: Null pointer dereference with large max_sectors_kb
Date: Fri, 18 Feb 2011 14:16:12 -0500 [thread overview]
Message-ID: <1298056463-sup-4453@think> (raw)
In-Reply-To: <20110218174315.GD5615@twin.jikos.cz>
Excerpts from David Sterba's message of 2011-02-18 12:43:15 -0500:
[ great analysis, thanks so much ]
>
> Could be, that any of the devices from 'head' list does not satisfy condition
> on line 619, but it cannot be the first device, as !latest_transid would
> work. There is only one device, /dev/sdb, latest_bdev is set and later on
> set on line 660.
>
> /me sees no more options
>
> Meanwhile I've tried it myself and the error does not happen here, with
> head at 795abaf1e4e185 (.38-rc4-178-g795abaf). I'll try it with latest -rc5.
>
> > > [ 605.110089] PGD 277d70067 PUD 277e0a067 PMD 0
> > > [ 605.110247] Oops: 0000 [#1] SMP
Are there any more kernel messages involved before the oops starts? It
really feels like we're failing to open the block device somehow inside
the btrfs scanning code.
-chris
next prev parent reply other threads:[~2011-02-18 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29302-10286@https.bugzilla.kernel.org/>
2011-02-17 23:37 ` [Bugme-new] [Bug 29302] New: Null pointer dereference with large max_sectors_kb Andrew Morton
2011-02-18 17:43 ` David Sterba
2011-02-18 19:16 ` Chris Mason [this message]
2011-02-18 19:56 ` Andrew Morton
2011-02-18 20:18 ` Chris Mason
2011-02-20 11:06 ` Tomas Zvala
2011-02-21 15:08 ` Chris Mason
2011-02-28 12:26 ` Tomas Zvala
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=1298056463-sup-4453@think \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dave@jikos.cz \
--cc=fox@murder.cz \
--cc=linux-btrfs@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.