All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Jeff Moyer <jmoyer@redhat.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Suren Baghdasaryan <surenb@google.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: mm: gdb fails if binary is on a DAX-enabled filesystem
Date: Fri, 19 Nov 2021 10:17:50 +0900	[thread overview]
Message-ID: <YZb7PgQ6Bw26cpsh@google.com> (raw)

Hello,

We are running into issues on a DAX enabled system: both
__copy_from_user_inatomic() fail.

[   28.914865] ------------[ cut here ]------------
[   28.915800] WARNING: CPU: 0 PID: 106 at mm/memory.c:2822 wp_page_copy+0x136/0x320
[   28.916857] CPU: 0 PID: 106 Comm: gdb Not tainted 5.15.0-01277-g6be711548944 #1
[   28.917823] Hardware name: ChromiumOS crosvm, BIOS 0 
[   28.918455] RIP: 0010:wp_page_copy+0x136/0x320
[   28.919001] Code: f1 79 00 4c 89 7b 50 48 8b 43 38 31 d2 49 39 07 75 23 48 8b 7d c8 48 8b 75 c0 ba 00 10 00 00 e8 6f 23 78 00 b2 01 85 c0 74 0b <0f> 0b 48 8b 7d c8 e8 8e 1f 78 00 48 8b 7b 58 88 55 c8 e8 2e f2 79
[   28.920642] RSP: 0018:ffffc900005dfbd8 EFLAGS: 00010206
[   28.921135] RAX: 0000000000001000 RBX: ffffc900005dfc40 RCX: 0000000000001000
[   28.921762] RDX: 0000000000001001 RSI: 0000000000448000 RDI: ffff8880007bb000
[   28.922410] RBP: ffffc900005dfc28 R08: ffff8880031884c8 R09: 0000000000000000
[   28.923058] R10: ffff88800f8234c8 R11: 0000000000000000 R12: ffffea000001eec0
[   28.923718] R13: 0000000000000000 R14: ffff88800e18e630 R15: ffff888000884240
[   28.924404] FS:  00007e5b49744180(0000) GS:ffff88800f800000(0000) knlGS:0000000000000000
[   28.925146] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   28.925688] CR2: 0000000000448000 CR3: 000000000e0d6000 CR4: 0000000000350eb0
[   28.926368] Call Trace:
[   28.926622]  __handle_mm_fault+0x67e/0xbd7
[   28.927018]  handle_mm_fault+0x16b/0x23d
[   28.927390]  __get_user_pages+0x2d6/0x4b7
[   28.927797]  __get_user_pages_remote+0xbe/0x20c
[   28.928224]  __access_remote_vm+0xb3/0x1c8
[   28.928655]  ptrace_access_vm+0x97/0xb0
[   28.929036]  generic_ptrace_pokedata+0x22/0x31
[   28.929452]  arch_ptrace+0x1ce/0x1dd
[   28.929801]  __do_sys_ptrace+0xa9/0xda
[   28.930161]  do_syscall_64+0x75/0x8b
[   28.930511]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   28.930996] RIP: 0033:0x7e5b4c86fe5a
[   28.931332] Code: 70 41 83 f8 03 c7 44 24 10 08 00 00 00 48 89 44 24 18 48 8d 44 24 30 8b 70 08 4c 0f 43 d1 48 89 44 24 20 b8 65 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 3e 48 85 c0 78 06 41 83 f8 02 76 1b 48 8b 4c
[   28.933086] RSP: 002b:00007ffdc3369150 EFLAGS: 00000202 ORIG_RAX: 0000000000000065
[   28.933767] RAX: ffffffffffffffda RBX: 0000000000448620 RCX: 00007e5b4c86fe5a
[   28.934476] RDX: 0000000000448620 RSI: 000000000000006d RDI: 0000000000000005
[   28.935206] RBP: 0000000000000001 R08: 0000000000000004 R09: 0000000000448620
[   28.935916] R10: 00841f0f2e6666cc R11: 0000000000000202 R12: 0000000000000001
[   28.936672] R13: 00841f0f2e6666cc R14: 0000000000000000 R15: 00007e5b49743958
[   28.937389] ---[ end trace 2808c0ffd7259839 ]---
Program received signal SIGSEGV, Segmentation fault.

Is there anything we can do about it?

             reply	other threads:[~2021-11-19  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19  1:17 Sergey Senozhatsky [this message]
2021-11-19  1:35 ` mm: gdb fails if binary is on a DAX-enabled filesystem Dan Williams
2021-11-19  2:07   ` Sergey Senozhatsky

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=YZb7PgQ6Bw26cpsh@google.com \
    --to=senozhatsky@chromium.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jmoyer@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=surenb@google.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.