linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Alexandre Ferrieux <alexandre.ferrieux@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-trace-users@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Bug: broken /proc/kcore in 6.13
Date: Fri, 17 Jan 2025 16:31:54 +0000	[thread overview]
Message-ID: <9f3ba47b-e0ce-4d7a-b60f-e5b8d96b0f2b@lucifer.local> (raw)
In-Reply-To: <ef3f7784-7129-436a-a5f7-1630b278b101@orange.com>

On Fri, Jan 17, 2025 at 04:28:32PM +0100, Alexandre Ferrieux wrote:
>
>
> On 17/01/2025 16:19, Alexandre Ferrieux wrote:
> > On 17/01/2025 15:44, Lorenzo Stoakes wrote:
> >>> Alexandre Ferrieux <alexandre.ferrieux@gmail.com> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Somewhere in the 6.13 branch (not bisected yet, sorry), it stopped being
> >>>> possible to disassemble the running kernel from gdb through /proc/kcore.
> >> Thanks for the report! Much appreciated.
> >>
> >> I may try to bisect here also unless you're close to finding the commit that
> >> broke this?
> >
> > I'm currently homing in on copy_page_to_iter_nofault(), will report shortly :)
>
> Hmm, actually, that baby ain't cooperative:
>
>   [Fri Jan 17 15:23:05 2025] trace_kprobe: Could not probe notrace function
>   copy_page_to_iter_nofault
>
> ... if I cannot insert kprobes to sniff around, I'm a bit stuck :}
> So I think you'll reach the goal faster than me !
>
> PS: For your bisection: the last working kernel I know of is Debian's 6.12 final:
>
>   ii  linux-image-6.12.9-amd64         6.12.9-1                         amd64
>     Linux 6.12 for 64-bit PCs (signed)
>
>

Cheers much appreciated, have been able to repro and am bisecting now! Will
update with results when done.


  reply	other threads:[~2025-01-17 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <05ea473e-d7e9-4ca5-ad91-ba8c00618fb4@orange.com>
2025-01-17 13:40 ` Steven Rostedt
2025-01-17 14:44   ` Lorenzo Stoakes
2025-01-17 15:19     ` Alexandre Ferrieux
2025-01-17 15:28       ` Alexandre Ferrieux
2025-01-17 16:31         ` Lorenzo Stoakes [this message]
2025-01-17 18:13           ` Lorenzo Stoakes
2025-01-17 19:27             ` Alexandre Ferrieux

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=9f3ba47b-e0ce-4d7a-b60f-e5b8d96b0f2b@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=alexandre.ferrieux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=rostedt@goodmis.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