All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jiangfeng Xiao <xiaojiangfeng@huawei.com>
Cc: linus.walleij@linaro.org, arnd@arndb.de, keescook@chromium.org,
	haibo.li@mediatek.com, angelogioacchino.delregno@collabora.com,
	amergnat@baylibre.com, akpm@linux-foundation.org,
	dave.hansen@linux.intel.com, douzhaolei@huawei.com,
	gustavoars@kernel.org, jpoimboe@kernel.org,
	kepler.chenxin@huawei.com, kirill.shutemov@linux.intel.com,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	nixiaoming@huawei.com, peterz@infradead.org,
	wangbing6@huawei.com, wangfangpeng1@huawei.com, jannh@google.com,
	willy@infradead.org, David.Laight@aculab.com
Subject: Re: [PATCH v3] ARM: unwind: improve unwinders for noreturn case
Date: Wed, 20 Mar 2024 19:42:44 +0000	[thread overview]
Message-ID: <Zfs8NNlAwF3+LYZ/@shell.armlinux.org.uk> (raw)
In-Reply-To: <1710949294-29287-1-git-send-email-xiaojiangfeng@huawei.com>

On Wed, Mar 20, 2024 at 11:41:34PM +0800, Jiangfeng Xiao wrote:
> This is an off-by-one bug which is common in unwinders,
> due to the fact that the address on the stack points
> to the return address rather than the call address.
> 
> So, for example, when the last instruction of a function
> is a function call (e.g., to a noreturn function), it can
> cause the unwinder to incorrectly try to unwind from
> the function after the callee.
> 
> foo:
> ...
>     bl      bar
> ... end of function and thus next function ...
> 
> which results in LR pointing into the next function.
> 
> Fixed this by subtracting 1 from frmae->pc in the call frame
> like ORC on x86 does.
> 
> Refer to the unwind_next_frame function in the unwind_orc.c

This came in while I was still replying to your previous reply, so
I'm going to ignore this. Please allow at least 24 hours between
postings, and please allow discussion to finish before posting a
new version - give your reviewers adequate time to compose a reply
bearing in mind that timezones might get in the way, but also making
supper (as is the case in this instance) may cause several hour delay
in reply.

Thanks.

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

WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jiangfeng Xiao <xiaojiangfeng@huawei.com>
Cc: linus.walleij@linaro.org, arnd@arndb.de, keescook@chromium.org,
	haibo.li@mediatek.com, angelogioacchino.delregno@collabora.com,
	amergnat@baylibre.com, akpm@linux-foundation.org,
	dave.hansen@linux.intel.com, douzhaolei@huawei.com,
	gustavoars@kernel.org, jpoimboe@kernel.org,
	kepler.chenxin@huawei.com, kirill.shutemov@linux.intel.com,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	nixiaoming@huawei.com, peterz@infradead.org,
	wangbing6@huawei.com, wangfangpeng1@huawei.com, jannh@google.com,
	willy@infradead.org, David.Laight@aculab.com
Subject: Re: [PATCH v3] ARM: unwind: improve unwinders for noreturn case
Date: Wed, 20 Mar 2024 19:42:44 +0000	[thread overview]
Message-ID: <Zfs8NNlAwF3+LYZ/@shell.armlinux.org.uk> (raw)
In-Reply-To: <1710949294-29287-1-git-send-email-xiaojiangfeng@huawei.com>

On Wed, Mar 20, 2024 at 11:41:34PM +0800, Jiangfeng Xiao wrote:
> This is an off-by-one bug which is common in unwinders,
> due to the fact that the address on the stack points
> to the return address rather than the call address.
> 
> So, for example, when the last instruction of a function
> is a function call (e.g., to a noreturn function), it can
> cause the unwinder to incorrectly try to unwind from
> the function after the callee.
> 
> foo:
> ...
>     bl      bar
> ... end of function and thus next function ...
> 
> which results in LR pointing into the next function.
> 
> Fixed this by subtracting 1 from frmae->pc in the call frame
> like ORC on x86 does.
> 
> Refer to the unwind_next_frame function in the unwind_orc.c

This came in while I was still replying to your previous reply, so
I'm going to ignore this. Please allow at least 24 hours between
postings, and please allow discussion to finish before posting a
new version - give your reviewers adequate time to compose a reply
bearing in mind that timezones might get in the way, but also making
supper (as is the case in this instance) may cause several hour delay
in reply.

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps 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

  reply	other threads:[~2024-03-20 19:43 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  1:39 [PATCH] usercopy: delete __noreturn from usercopy_abort Jiangfeng Xiao
2024-03-04 15:15 ` Jann Horn
2024-03-04 17:40   ` Kees Cook
2024-03-05  3:31     ` Jiangfeng Xiao
2024-03-05  9:32       ` Kees Cook
2024-03-05 11:38         ` Jiangfeng Xiao
2024-03-05 17:58           ` Josh Poimboeuf
2024-03-05 17:58             ` Josh Poimboeuf
2024-03-06  4:00             ` Jiangfeng Xiao
2024-03-06  4:00               ` Jiangfeng Xiao
2024-03-06  9:52             ` Russell King (Oracle)
2024-03-06  9:52               ` Russell King (Oracle)
2024-03-06 16:02               ` Josh Poimboeuf
2024-03-06 16:02                 ` Josh Poimboeuf
2024-03-09 14:58               ` David Laight
2024-03-09 14:58                 ` David Laight
2024-03-18  4:01             ` Jiangfeng Xiao
2024-03-18  4:01               ` Jiangfeng Xiao
2024-03-05  2:54   ` Jiangfeng Xiao
2024-03-05  3:12     ` Jiangfeng Xiao
2024-03-20  2:19 ` [PATCH] ARM: unwind: improve unwinders for noreturn case Jiangfeng Xiao
2024-03-20  2:19   ` Jiangfeng Xiao
2024-03-20  2:46   ` Kees Cook
2024-03-20  2:46     ` Kees Cook
2024-03-20  3:30     ` Jiangfeng Xiao
2024-03-20  3:30       ` Jiangfeng Xiao
2024-03-20  3:34       ` Matthew Wilcox
2024-03-20  3:34         ` Matthew Wilcox
2024-03-20  3:46         ` Jiangfeng Xiao
2024-03-20  3:46           ` Jiangfeng Xiao
2024-03-20  3:44 ` [PATCH v2] " Jiangfeng Xiao
2024-03-20  3:44   ` Jiangfeng Xiao
2024-03-20  8:45   ` Russell King (Oracle)
2024-03-20  8:45     ` Russell King (Oracle)
2024-03-20 15:30     ` Jiangfeng Xiao
2024-03-20 15:30       ` Jiangfeng Xiao
2024-03-20 19:40       ` Russell King (Oracle)
2024-03-20 19:40         ` Russell King (Oracle)
2024-03-21  9:44         ` Jiangfeng Xiao
2024-03-21  9:44           ` Jiangfeng Xiao
2024-03-21 10:22           ` David Laight
2024-03-21 10:22             ` David Laight
2024-03-21 11:23             ` Russell King (Oracle)
2024-03-21 11:23               ` Russell King (Oracle)
2024-03-21 12:07               ` David Laight
2024-03-21 12:07                 ` David Laight
2024-03-21 12:22                 ` Russell King (Oracle)
2024-03-21 12:22                   ` Russell King (Oracle)
2024-03-21 12:57                   ` David Laight
2024-03-21 12:57                     ` David Laight
2024-03-21 13:08                     ` Russell King (Oracle)
2024-03-21 13:08                       ` Russell King (Oracle)
2024-03-21 14:37                       ` David Laight
2024-03-21 14:37                         ` David Laight
2024-03-21 14:56                         ` Russell King (Oracle)
2024-03-21 14:56                           ` Russell King (Oracle)
2024-03-21 15:20                           ` David Laight
2024-03-21 15:20                             ` David Laight
2024-03-21 15:33                             ` Russell King (Oracle)
2024-03-21 15:33                               ` Russell King (Oracle)
2024-03-21 22:43               ` Ard Biesheuvel
2024-03-21 22:43                 ` Ard Biesheuvel
2024-03-22  0:08                 ` Russell King (Oracle)
2024-03-22  0:08                   ` Russell King (Oracle)
2024-03-22  9:24                   ` David Laight
2024-03-22  9:24                     ` David Laight
2024-03-22  9:52                     ` Russell King (Oracle)
2024-03-22  9:52                       ` Russell King (Oracle)
2024-03-22 12:54                       ` Jiangfeng Xiao
2024-03-22 12:54                         ` Jiangfeng Xiao
2024-03-22 14:16                       ` David Laight
2024-03-22 14:16                         ` David Laight
2024-03-20 15:41 ` [PATCH v3] " Jiangfeng Xiao
2024-03-20 15:41   ` Jiangfeng Xiao
2024-03-20 19:42   ` Russell King (Oracle) [this message]
2024-03-20 19:42     ` 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=Zfs8NNlAwF3+LYZ/@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=David.Laight@aculab.com \
    --cc=akpm@linux-foundation.org \
    --cc=amergnat@baylibre.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=arnd@arndb.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=douzhaolei@huawei.com \
    --cc=gustavoars@kernel.org \
    --cc=haibo.li@mediatek.com \
    --cc=jannh@google.com \
    --cc=jpoimboe@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kepler.chenxin@huawei.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nixiaoming@huawei.com \
    --cc=peterz@infradead.org \
    --cc=wangbing6@huawei.com \
    --cc=wangfangpeng1@huawei.com \
    --cc=willy@infradead.org \
    --cc=xiaojiangfeng@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.