All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ARM: mm: Provide better message when kernel fault
Date: Mon, 10 Oct 2022 16:55:51 +0100	[thread overview]
Message-ID: <Y0RAh/6e60fXUex6@shell.armlinux.org.uk> (raw)
In-Reply-To: <4339e1f4-b5c1-0b61-3a37-e63aafe22857@huawei.com>

On Mon, Oct 10, 2022 at 07:24:15PM +0800, Kefeng Wang wrote:
> 
> On 2022/9/27 14:21, Kefeng Wang wrote:
> > If there is a kernel fault, see do_kernel_fault(), we only print
> > the generic "paging request" or "NULL pointer dereference" message
> > which don't show read, write or excute information, let's provide
> > better fault message for them.
> 
> Hi Russell, what's your option about this one, if no object,

LGTM.

> I will send to ARM patch system, thanks,

Yes please, if not already done.

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ARM: mm: Provide better message when kernel fault
Date: Mon, 10 Oct 2022 16:55:51 +0100	[thread overview]
Message-ID: <Y0RAh/6e60fXUex6@shell.armlinux.org.uk> (raw)
In-Reply-To: <4339e1f4-b5c1-0b61-3a37-e63aafe22857@huawei.com>

On Mon, Oct 10, 2022 at 07:24:15PM +0800, Kefeng Wang wrote:
> 
> On 2022/9/27 14:21, Kefeng Wang wrote:
> > If there is a kernel fault, see do_kernel_fault(), we only print
> > the generic "paging request" or "NULL pointer dereference" message
> > which don't show read, write or excute information, let's provide
> > better fault message for them.
> 
> Hi Russell, what's your option about this one, if no object,

LGTM.

> I will send to ARM patch system, thanks,

Yes please, if not already done.

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2022-10-10 15:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 10:38 [PATCH v2] ARM: mm: Provide better fault message for permission fault Kefeng Wang
2022-09-19 10:38 ` Kefeng Wang
2022-09-26 10:13 ` Russell King (Oracle)
2022-09-26 10:13   ` Russell King (Oracle)
2022-09-26 13:26   ` Kefeng Wang
2022-09-26 13:26     ` Kefeng Wang
2022-09-26 14:15     ` Russell King (Oracle)
2022-09-26 14:15       ` Russell King (Oracle)
2022-09-27  6:21   ` [PATCH v3] ARM: mm: Provide better message when kernel fault Kefeng Wang
2022-09-27  6:21     ` Kefeng Wang
2022-10-10 11:24     ` Kefeng Wang
2022-10-10 11:24       ` Kefeng Wang
2022-10-10 15:55       ` Russell King (Oracle) [this message]
2022-10-10 15:55         ` Russell King (Oracle)

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=Y0RAh/6e60fXUex6@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangkefeng.wang@huawei.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.