From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
Hajime Tazaki <thehajime@gmail.com>
Cc: rrs@debian.org, chris.obbard@collabora.com,
linux-um@lists.infradead.org, 983379@bugs.debian.org
Subject: Re: linux uml segfault
Date: Fri, 05 Mar 2021 21:06:35 +0100 [thread overview]
Message-ID: <d657cc169ff8fee29353cf473f5c4093c374ecc8.camel@sipsolutions.net> (raw)
In-Reply-To: <02a1bb6c-3727-61d6-d0bb-a2200f1b0d14@kot-begemot.co.uk>
On Fri, 2021-03-05 at 19:03 +0000, Anton Ivanov wrote:
>
> I thought of that, but surrendered to the "dark side" of the quick and ugly fix.
:)
> We can do that for the ipc/sem.c - it brings in uaccess.h which
> ultimately pulls uaccess from our asm tree. So if we do it there, it
> will end up in sem.c
Well, most easily you could do it in ipc/util.h, where it's declared. Or
any place that is pulled in by it, e.g. even asm/errno.h.
All ugly though.
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-03-05 20:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 8:06 linux uml segfault Ritesh Raj Sarraf
2021-02-23 10:50 ` Anton Ivanov
2021-02-23 12:12 ` Christopher Obbard
2021-02-23 12:24 ` Anton Ivanov
2021-02-23 17:19 ` Anton Ivanov
2021-02-23 17:26 ` Ritesh Raj Sarraf
2021-02-23 18:02 ` Anton Ivanov
2021-02-24 11:44 ` Anton Ivanov
2021-03-02 9:09 ` Ritesh Raj Sarraf
2021-03-02 11:34 ` Anton Ivanov
2021-03-02 14:23 ` Ritesh Raj Sarraf
2021-03-02 17:05 ` Anton Ivanov
2021-03-02 17:27 ` Ritesh Raj Sarraf
2021-03-03 9:30 ` Anton Ivanov
2021-03-03 10:45 ` Bug#983379: " Ritesh Raj Sarraf
2021-03-03 10:53 ` Anton Ivanov
2021-03-03 22:40 ` Johannes Berg
2021-03-04 5:38 ` Hajime Tazaki
2021-03-04 7:45 ` Anton Ivanov
2021-03-04 7:47 ` Johannes Berg
2021-03-04 8:05 ` Benjamin Berg
2021-03-04 18:41 ` Anton Ivanov
2021-03-05 9:59 ` Anton Ivanov
2021-03-05 10:07 ` Johannes Berg
2021-03-05 17:39 ` Anton Ivanov
2021-03-05 18:32 ` Johannes Berg
2021-03-05 19:03 ` Anton Ivanov
2021-03-05 20:06 ` Johannes Berg [this message]
2021-03-05 20:07 ` Johannes Berg
2021-03-05 20:22 ` Johannes Berg
2021-03-05 22:25 ` Hajime Tazaki
2021-03-07 12:22 ` Hajime Tazaki
2021-03-07 12:56 ` Johannes Berg
2021-03-04 7:28 ` Anton Ivanov
2021-03-04 7:43 ` Johannes Berg
2021-03-05 19:54 ` Johannes Berg
2021-03-05 20:43 ` [PATCH] um: mark all kernel symbols as local Johannes Berg
2021-03-05 20:54 ` Anton Ivanov
2021-03-06 10:51 ` Ritesh Raj Sarraf
2021-03-08 10:29 ` Bug#983379: " Ritesh Raj Sarraf
2021-03-08 10:33 ` Johannes Berg
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=d657cc169ff8fee29353cf473f5c4093c374ecc8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=983379@bugs.debian.org \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=chris.obbard@collabora.com \
--cc=linux-um@lists.infradead.org \
--cc=rrs@debian.org \
--cc=thehajime@gmail.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.