From: Alexey Dobriyan <adobriyan@gmail.com>
To: joel@joelfernandes.org
Cc: linux-kernel@vger.kernel.org, alexei.starovoitov@gmail.com
Subject: Re: [PATCH v2 1/2] Provide in-kernel headers for making it easy to extend the kernel
Date: Tue, 19 Feb 2019 09:05:31 +0300 [thread overview]
Message-ID: <20190219060531.GA3263@avx2> (raw)
> /proc/kheaders.txz
This is gross.
> The feature is also buildable as a module just in case the user desires
> it not being part of the kernel image. This makes it possible to load
> and unload the headers on demand. A tracing program, or a kernel module
> builder can load the module, do its operations, and then unload the
> module to save kernel memory.
Please explain how keeping headers on the filesystem is not OK due
to "licensing and other issues" but keeping a module on the filesystem
is OK.
> > I can route it via bpf-next tree if there are no objections.
Please don't.
IKHD_ST IKHD_ED are bogus artifacts as others mentioned.
proc_create(S_IFREG) is redundant.
seq_file.h is not needed as is THIS_MODULE.
I'd say such data should live in their own section for easy extraction
with "objdump -j", something /proc/config.gz never did.
next reply other threads:[~2019-02-19 6:05 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 6:05 Alexey Dobriyan [this message]
2019-02-19 17:25 ` [PATCH v2 1/2] Provide in-kernel headers for making it easy to extend the kernel Joel Fernandes
-- strict thread matches above, loose matches on Subject: below --
2019-02-11 14:35 Joel Fernandes (Google)
2019-02-11 14:35 ` Joel Fernandes (Google)
2019-02-11 14:35 ` joel
2019-02-13 22:50 ` Karim Yaghmour
2019-02-13 22:50 ` Karim Yaghmour
2019-02-13 22:50 ` karim.yaghmour
2019-02-15 3:19 ` Alexei Starovoitov
2019-02-15 3:19 ` Alexei Starovoitov
2019-02-15 3:19 ` alexei.starovoitov
2019-02-15 3:47 ` Joel Fernandes
2019-02-15 3:47 ` Joel Fernandes
2019-02-15 3:47 ` joel
2019-02-16 19:10 ` Manoj
2019-02-16 19:10 ` Manoj
2019-02-16 19:10 ` linux
2019-02-19 4:14 ` Masahiro Yamada
2019-02-19 4:14 ` Masahiro Yamada
2019-02-19 4:14 ` yamada.masahiro
2019-02-19 4:28 ` Alexei Starovoitov
2019-02-19 4:28 ` Alexei Starovoitov
2019-02-19 4:28 ` alexei.starovoitov
2019-02-19 4:34 ` Joel Fernandes
2019-02-19 4:34 ` Joel Fernandes
2019-02-19 4:34 ` joel
2019-02-19 4:42 ` Masahiro Yamada
2019-02-19 4:42 ` Masahiro Yamada
2019-02-19 4:42 ` yamada.masahiro
2019-02-19 5:12 ` Joel Fernandes
2019-02-19 5:12 ` Joel Fernandes
2019-02-19 5:12 ` joel
2019-02-19 15:16 ` Joel Fernandes
2019-02-19 15:16 ` Joel Fernandes
2019-02-19 15:16 ` joel
2019-02-21 14:34 ` Masahiro Yamada
2019-02-21 14:34 ` Masahiro Yamada
2019-02-21 14:34 ` yamada.masahiro
2019-02-21 15:29 ` Joel Fernandes
2019-02-21 15:29 ` Joel Fernandes
2019-02-21 15:29 ` joel
2019-03-25 13:49 ` Joel Fernandes
2019-03-25 13:49 ` Joel Fernandes
2019-03-25 13:49 ` joel
2019-03-27 17:31 ` Joel Fernandes
2019-03-27 17:31 ` Joel Fernandes
2019-03-27 17:31 ` joel
2019-04-03 7:48 ` Masahiro Yamada
2019-04-03 7:48 ` Masahiro Yamada
2019-04-03 7:48 ` yamada.masahiro
2019-04-03 17:20 ` Joel Fernandes
2019-04-03 17:20 ` Joel Fernandes
2019-04-03 17:20 ` joel
2019-04-03 17:46 ` Daniel Colascione
2019-04-03 17:46 ` Daniel Colascione
2019-04-03 17:46 ` dancol
2019-04-03 17:56 ` Joel Fernandes
2019-04-03 17:56 ` Joel Fernandes
2019-04-03 17:56 ` joel
2019-04-04 3:54 ` Masahiro Yamada
2019-04-04 3:54 ` Masahiro Yamada
2019-04-04 3:54 ` yamada.masahiro
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=20190219060531.GA3263@avx2 \
--to=adobriyan@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.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.