From: Matthew Wilcox <willy@infradead.org>
To: Mohan R <mohan43u@gmail.com>
Cc: uwe.sauter.de@gmail.com,
almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, ntfs3@lists.linux.dev
Subject: Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
Date: Sat, 27 Nov 2021 14:50:09 +0000 [thread overview]
Message-ID: <YaJFoadpGAwPfdLv@casper.infradead.org> (raw)
In-Reply-To: <CAFYqD2pe-sjPrHXGsNCHa2fcdECNm44UEZbEn4P5VgygFnrn7A@mail.gmail.com>
On Sat, Nov 27, 2021 at 07:43:06PM +0530, Mohan R wrote:
> Hi,
>
> I confirm this issue. I tried to rsync between two ntfs3 mounts, but
> rsync got killed unexpectedly.
This is a completely different problem.
> Nov 27 19:21:53 mohanlaptop0 kernel: BUG: unable to handle page fault
> for address: ffffb9c24fb74000
The address has nothing in common with the address in the original
report.
> Nov 27 19:21:53 mohanlaptop0 kernel: #PF: supervisor read access in kernel mode
> Nov 27 19:21:53 mohanlaptop0 kernel: #PF: error_code(0x0000) - not-present page
> Nov 27 19:21:53 mohanlaptop0 kernel: PGD 100000067 P4D 100000067 PUD
> 1001bd067 PMD 10460a067 PTE 0
> Nov 27 19:21:53 mohanlaptop0 kernel: Oops: 0000 [#2] PREEMPT SMP NOPTI
> Nov 27 19:21:53 mohanlaptop0 kernel: CPU: 5 PID: 144039 Comm: rsync
> Not tainted 5.15.5-arch1-1 #1 f0168f793e3f707b46715a62fafabd6a40826924
> Nov 27 19:21:53 mohanlaptop0 kernel: Hardware name: Dell Inc. Inspiron
> 14 5410/0CKN95, BIOS 2.2.1 07/27/2021
> Nov 27 19:21:53 mohanlaptop0 kernel: RIP: 0010:show_trace_log_lvl+0x1a4/0x32d
> Nov 27 19:21:53 mohanlaptop0 kernel: Code: c7 14 60 a5 86 e8 0f be 00
> 00 4d 85 ed 74 41 0f b6 95 37 ff ff ff 4c 89 f1 4c 89 ee 48 8d bd 50
> ff ff ff e8 dc fd ff ff eb 26 <4c> 8b 3b 48 8d bd 70 ff ff ff e8 2e 4e
> 52 ff 4c 89 ff 48 89 85 28
That's annoying. show_trace_log_lvl() isn't supposed to crash.
> Nov 27 19:21:53 mohanlaptop0 kernel: RSP: 0018:ffffb9c24fb738d8 EFLAGS: 00010012
> Nov 27 19:21:53 mohanlaptop0 kernel: RAX: 0000000000000000 RBX:
> ffffb9c24fb73fff RCX: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RDX: 0000000000000000 RSI:
> 0000000000000000 RDI: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RBP: ffffb9c24fb739b8 R08:
> 0000000000000000 R09: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: R10: 0000000000000000 R11:
> 0000000000000000 R12: ffff949c432b0000
> Nov 27 19:21:53 mohanlaptop0 kernel: R13: 0000000000000000 R14:
> ffffffff86a7d25f R15: 0000000000002b00
> Nov 27 19:21:53 mohanlaptop0 kernel: FS: 00007f40259b8580(0000)
> GS:ffff949dc7740000(0000) knlGS:0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> 0000000080050033
> Nov 27 19:21:53 mohanlaptop0 kernel: CR2: ffffb9c24fb74000 CR3:
> 00000001b114c005 CR4: 0000000000770ee0
> Nov 27 19:21:53 mohanlaptop0 kernel: PKRU: 55555554
> Nov 27 19:21:53 mohanlaptop0 kernel: Call Trace:
> Nov 27 19:21:53 mohanlaptop0 kernel: <TASK>
> Nov 27 19:21:53 mohanlaptop0 kernel: __die_body.cold+0x1a/0x1f
> Nov 27 19:21:53 mohanlaptop0 kernel: page_fault_oops+0x19e/0x310
> Nov 27 19:21:53 mohanlaptop0 kernel: exc_page_fault+0xda/0x180
> Nov 27 19:21:53 mohanlaptop0 kernel: asm_exc_page_fault+0x1e/0x30
> Nov 27 19:21:53 mohanlaptop0 kernel: RIP: 0010:0xffffff8586d685ff
> Nov 27 19:21:53 mohanlaptop0 kernel: Code: Unable to access opcode
> bytes at RIP 0xffffff8586d685d5.
> Nov 27 19:21:53 mohanlaptop0 kernel: RSP: 0018:ffffb9c24fb73b4f EFLAGS: 00010246
> Nov 27 19:21:53 mohanlaptop0 kernel: RAX: 0000000000000000 RBX:
> 0000000000001700 RCX: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RDX: 0000000000000000 RSI:
> 0000000000000000 RDI: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RBP: ffb9c24fb73c3800 R08:
> 0000000000000000 R09: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: R10: 0000000000000000 R11:
> 0000000000000000 R12: ff949b43a8426800
> Nov 27 19:21:53 mohanlaptop0 kernel: R13: 00000001112ccaff R14:
> fff6a0c99d400000 R15: 00000000000056ff
This is where the real bug happened. It would be helpful if you
could run
./scripts/faddr2line /path/to/vmlinux page_cache_ra_unbounded+0x1c5/0x250
It'll spit out something like:
page_cache_ra_unbounded at mm/readahead.c:241
but probably a different line number from that.
> Nov 27 19:21:53 mohanlaptop0 kernel: ? page_cache_ra_unbounded+0x1c5/0x250
> Nov 27 19:21:53 mohanlaptop0 kernel: ? filemap_get_pages+0x269/0x730
> Nov 27 19:21:53 mohanlaptop0 kernel: ? filemap_read+0xb9/0x360
> Nov 27 19:21:53 mohanlaptop0 kernel: ? new_sync_read+0x156/0x1f0
> Nov 27 19:21:53 mohanlaptop0 kernel: ? vfs_read+0xff/0x1a0
> Nov 27 19:21:53 mohanlaptop0 kernel: ? ksys_read+0x67/0xf0
next prev parent reply other threads:[~2021-11-27 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 14:13 Bug using new ntfs3 file system driver (5.15.2 on Arch Linux) Mohan R
2021-11-27 14:50 ` Matthew Wilcox [this message]
2021-12-28 20:45 ` August Wikerfors
2021-12-28 21:00 ` August Wikerfors
2021-12-29 1:13 ` Matthew Wilcox
2022-01-03 15:20 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2021-11-19 7:48 Uwe Sauter
2021-11-19 13:13 ` Matthew Wilcox
2021-11-19 14:19 ` Uwe Sauter
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=YaJFoadpGAwPfdLv@casper.infradead.org \
--to=willy@infradead.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mohan43u@gmail.com \
--cc=ntfs3@lists.linux.dev \
--cc=uwe.sauter.de@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.