lustre-devel-lustre.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Current results and status of my upstream work
Date: Sat, 31 Mar 2018 16:47:00 +1100	[thread overview]
Message-ID: <874lkw3igb.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <alpine.LFD.2.21.1803301844001.9681@casper.infradead.org>

On Fri, Mar 30 2018, James Simmons wrote:

>
> To let you know test 154 always triggers a LBUG due to splice changes that
> landed. I'm seeing
>
> 2018-03-30 13:41:37 [ 6351.749923] BUG: unable to handle kernel paging 
> request at ffffffffffffffbc
> 2018-03-30 13:41:37 [ 6351.757031] IP: ll_splice_alias+0x1df/0x250 
> [lustre]

Can you run
  ./scripts/faddr2line drivers/staging/lustre/lustre/llite/namei.o  ll_splice_alias+0x1df/0x250 

(you might need a different pathname for namei.o, depending on how you
build the kernel).

d_splice_alias() can return an error (very rarely I think) and the
CDEBUG() at the end of ll_splice_alias wouldn't be happy about that.

The code shows a crash at:
  2b:*	48 8b 48 30          	mov    0x30(%rax),%rcx		<-- trapping instruction

and 
   RAX: ffffffffffffff8c

which is -116 or -ESTALE.
That is an error which d_splice_alias() can get from __d_unalias, so
I guess that is what is happening.

I'll dig through d_splice_alias() and try to work out what that means.

Thanks,
NeilBrown
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20180331/510a5e99/attachment.sig>

  reply	other threads:[~2018-03-31  5:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 23:17 [lustre-devel] Lustre upstream client TODO list James Simmons
2018-02-11 23:54 ` NeilBrown
2018-02-12  1:15   ` Patrick Farrell
2018-02-12  2:09     ` NeilBrown
2018-03-22 23:21   ` [lustre-devel] Current results and status of my upstream work James Simmons
2018-03-27  5:32     ` NeilBrown
2018-03-27  6:17       ` Dilger, Andreas
2018-03-27 21:17         ` Jinshan Xiong
2018-03-27 21:58           ` NeilBrown
2018-03-30 18:55       ` James Simmons
2018-03-31  5:47         ` NeilBrown [this message]
2019-12-19  5:31 ` [lustre-devel] Lustre upstreaming status NeilBrown
2019-12-27 16:04   ` Degremont, Aurelien
2020-01-07  0:02   ` James Simmons
2020-01-07  1:53     ` Andreas Dilger
2020-01-07  2:24       ` Andreas Dilger
2020-01-07  4:32       ` NeilBrown
2020-01-07  4:05     ` NeilBrown
2020-01-08 21:18       ` NeilBrown

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=874lkw3igb.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=lustre-devel@lists.lustre.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).