From: Al Viro <viro@zeniv.linux.org.uk>
To: Vicente Bergas <vicencb@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: d_lookup: Unable to handle kernel paging request
Date: Tue, 18 Jun 2019 19:48:21 +0100 [thread overview]
Message-ID: <20190618184821.GC17978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190618183548.GB17978@ZenIV.linux.org.uk>
On Tue, Jun 18, 2019 at 07:35:48PM +0100, Al Viro wrote:
> So far it looks like something is buggering a forward reference
> in hash chain in a fairly specific way - the values seen had been
> 00000000010000000 and
> 00008800010000000. Does that smell like anything from arm64-specific
> data structures (PTE, etc.)?
make that 0000000001000000 and 0000880001000000 resp. Tests in the
patch are correct, just mistyped it here...
> Alternatively, we might've gone off rails a step (or more) before,
> with the previous iteration going through bogus, but at least mapped
> address - the one that has never been a dentry in the first place.
next prev parent reply other threads:[~2019-06-18 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 10:40 d_lookup: Unable to handle kernel paging request Vicente Bergas
2019-05-22 13:53 ` Al Viro
2019-05-22 15:44 ` Vicente Bergas
2019-05-22 16:29 ` Al Viro
2019-05-24 22:21 ` Vicente Bergas
2019-05-28 9:38 ` Vicente Bergas
2019-06-18 18:35 ` Al Viro
2019-06-18 18:48 ` Al Viro [this message]
2019-06-19 12:42 ` Vicente Bergas
2019-06-19 16:28 ` Al Viro
2019-06-19 16:51 ` Vicente Bergas
2019-06-19 17:06 ` Will Deacon
2019-06-19 17:09 ` Al Viro
2019-06-22 18:02 ` Vicente Bergas
2019-06-24 11:47 ` Will Deacon
2019-06-25 9:46 ` Will Deacon
2019-06-25 10:48 ` Vicente Bergas
2019-06-29 22:56 ` Vicente Bergas
2019-06-19 17:04 ` Will Deacon
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=20190618184821.GC17978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vicencb@gmail.com \
/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.