From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: tglx@linutronix.de, hch@infradead.org, mingo@redhat.com,
keescook@chromium.org, arnd@arndb.de, luto@amacapital.net,
wad@chromium.org, rostedt@goodmis.org, paul@paul-moore.com,
eparis@redhat.com, oleg@redhat.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
kernel@collabora.com,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag
Date: Tue, 24 Nov 2020 12:55:39 -0500 [thread overview]
Message-ID: <87360yprl0.fsf@collabora.com> (raw)
In-Reply-To: <20646400-0e16-0eb5-c829-3b77df8c38e3@gmail.com> (Dmitry Osipenko's message of "Tue, 24 Nov 2020 19:28:24 +0300")
Dmitry Osipenko <digetx@gmail.com> writes:
> Hi,
>
> This patch broke seccomp on arm32 using linux-next, chromium browser
> doesn't work anymore and there are these errors in KMSG:
>
> Unhandled prefetch abort: breakpoint debug exception (0x002) at ...
>
> Note that arm doesn't use CONFIG_GENERIC_ENTRY. Please fix, thanks in
> advance.
Hi Dmitry,
I believe this is the same problem reported yesterday on this thread
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2390444.html
can you please try the patch I shared on that thread?
https://lore.kernel.org/patchwork/patch/1344098/
Thanks,
--
Gabriel Krisman Bertazi
WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: linux-arch@vger.kernel.org, wad@chromium.org,
keescook@chromium.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, x86@kernel.org, oleg@redhat.com,
rostedt@goodmis.org, luto@amacapital.net, hch@infradead.org,
mingo@redhat.com, eparis@redhat.com,
Russell King - ARM Linux <linux@armlinux.org.uk>,
tglx@linutronix.de, kernel@collabora.com,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
paul@paul-moore.com
Subject: Re: [PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag
Date: Tue, 24 Nov 2020 12:55:39 -0500 [thread overview]
Message-ID: <87360yprl0.fsf@collabora.com> (raw)
In-Reply-To: <20646400-0e16-0eb5-c829-3b77df8c38e3@gmail.com> (Dmitry Osipenko's message of "Tue, 24 Nov 2020 19:28:24 +0300")
Dmitry Osipenko <digetx@gmail.com> writes:
> Hi,
>
> This patch broke seccomp on arm32 using linux-next, chromium browser
> doesn't work anymore and there are these errors in KMSG:
>
> Unhandled prefetch abort: breakpoint debug exception (0x002) at ...
>
> Note that arm doesn't use CONFIG_GENERIC_ENTRY. Please fix, thanks in
> advance.
Hi Dmitry,
I believe this is the same problem reported yesterday on this thread
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2390444.html
can you please try the patch I shared on that thread?
https://lore.kernel.org/patchwork/patch/1344098/
Thanks,
--
Gabriel Krisman Bertazi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-24 17:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 17:41 [PATCH v2 00/10] Migrate syscall entry/exit work to SYSCALL_WORK flagset Gabriel Krisman Bertazi
2020-11-16 17:41 ` [PATCH v2 01/10] x86: Expose syscall_work field in thread_info Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:41 ` [PATCH v2 02/10] entry: Expose helpers to migrate TIF to SYSCALL_WORK flags Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:41 ` [PATCH v2 03/10] entry: Wire up syscall_work in common entry code Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:42 ` [PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-24 16:28 ` [PATCH v2 04/10] " Dmitry Osipenko
2020-11-24 16:28 ` Dmitry Osipenko
2020-11-24 17:55 ` Gabriel Krisman Bertazi [this message]
2020-11-24 17:55 ` Gabriel Krisman Bertazi
2020-11-24 18:41 ` Dmitry Osipenko
2020-11-24 18:41 ` Dmitry Osipenko
2020-11-16 17:42 ` [PATCH v2 05/10] tracepoints: " Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-17 19:11 ` [PATCH v2 05/10] " Steven Rostedt
2020-11-16 17:42 ` [PATCH v2 06/10] ptrace: Migrate to use SYSCALL_TRACE flag Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:42 ` [PATCH v2 07/10] ptrace: Migrate TIF_SYSCALL_EMU to use SYSCALL_WORK flag Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:42 ` [PATCH v2 08/10] audit: Migrate " Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:42 ` [PATCH v2 09/10] entry: Drop usage of TIF flags in the generic syscall code Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
2020-11-16 17:42 ` [PATCH v2 10/10] x86: Reclaim unused x86 TI flags Gabriel Krisman Bertazi
2020-11-16 21:11 ` [tip: core/entry] " tip-bot2 for Gabriel Krisman Bertazi
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=87360yprl0.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=arnd@arndb.de \
--cc=digetx@gmail.com \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paul@paul-moore.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wad@chromium.org \
--cc=x86@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 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.