linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Ferrieux <alexandre.ferrieux@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	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, Mike Rapoport <rppt@kernel.org>
Subject: Re: Bug: broken /proc/kcore in 6.13
Date: Fri, 17 Jan 2025 20:27:56 +0100	[thread overview]
Message-ID: <3719ee8a-38ef-4aaa-aca4-b6d82df51661@orange.com> (raw)
In-Reply-To: <ecb22f03-ca7f-4212-9f02-cceafb9cfb7f@lucifer.local>

On 17/01/2025 19:13, Lorenzo Stoakes wrote:
> 
> +cc Mike
> 
> OK so nothing to worry about here - the feature that causes this problem
> has been completely disabled. This may not be in Linus's tree yet but will
> be for 6.13 release [0].
> 
> I think the vread_iter() check for 0 can wait for 6.14, as once the area of
> memory is identified this should never happen, but we do want to pick up on
> it, with a WARN_ON_ONCE() to catch stuff like this right away.
> 
> Thanks so much for the repro, though I observed the 'core /proc/kcore'
> command freezing up before any 'disass' in my qemu setup, interestingly!
> 
> [0]:https://lore.kernel.org/all/20250113112934.GA8385@noisy.programming.kicks-ass.net/

Thank you for the fast fix, I'm back on track :)

 Dump of assembler code for function ice_process_skb_fields:
    0xffffffffc0fc1eb0 <+0>:     nopw   (%rax)
    0xffffffffc0fc1eb4 <+4>:     nopl   0x0(%rax,%rax,1)
    0xffffffffc0fc1eb9 <+9>:     push   %r14
    0xffffffffc0fc1ebb <+11>:    push   %r13

-Alex



      reply	other threads:[~2025-01-17 19:28 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
2025-01-17 18:13           ` Lorenzo Stoakes
2025-01-17 19:27             ` Alexandre Ferrieux [this message]

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=3719ee8a-38ef-4aaa-aca4-b6d82df51661@orange.com \
    --to=alexandre.ferrieux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.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