public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	"Jose E. Marchesi" <jemarch@gnu.org>,
	linux-toolchains@vger.kernel.org,
	clang-built-linux <llvm@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: plumbers session on syscall wrapping and kernel header libc circular depdence?
Date: Tue, 19 Apr 2022 12:46:48 +0200	[thread overview]
Message-ID: <87lew14ag7.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAKwvOdmwyFDYKMpq0dcvbq06drtZonpNJ3PqLx2RMBE00beHZA@mail.gmail.com> (Nick Desaulniers's message of "Fri, 15 Apr 2022 10:48:13 -0700")

* Nick Desaulniers:

> Hi Florian, Arnd, and Masahiro,
> Jose and I are currently in the planning process to put together a
> Kernel+Toolchain microconference track at Linux Plumbers Conference
> this year (Sept 12-14) in Dublin, Ireland.

I'm not sure if I will be able to travel by that time.

> Would you all be interested in a session (if you're planning on
> attending) discussing syscall wrapping for libc's and UAPI circular
> dependency on the libc?
>
> Masahiro and I were recently discussing the feasibility of building
> the kernel UAPI header tests with -nostdinc, but there are some
> interesting complications perhaps worth sharing with others?

To be honest, that doesn't seem to be a good use of a session slot.
Surely we can figure out a way to solve this issue offline (and if it's
a problem worth solving)?

(I expect that using -nostdinc makes it more difficult to support
compilers which are not GCC-compatible.)

Thanks,
Florian


  reply	other threads:[~2022-04-19 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 17:48 plumbers session on syscall wrapping and kernel header libc circular depdence? Nick Desaulniers
2022-04-19 10:46 ` Florian Weimer [this message]
2022-04-25  4:43 ` Masahiro Yamada
2022-04-25 17:51   ` Nick Desaulniers

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=87lew14ag7.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=arnd@kernel.org \
    --cc=carlos@redhat.com \
    --cc=jemarch@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox