[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+Eo-ewWL2_RtBaVN9msAdA3Pgu8H7uBxVcc=b5DMBy5g@mail.gmail.com>
Date: Mon, 6 May 2019 09:11:30 -0700
From: Kees Cook <keescook@...omium.org>
To: Allen <allen.lkml@...il.com>
Cc: Kernel Hardening <kernel-hardening@...ts.openwall.com>, tglx@...uxtronix.de
Subject: Re: [RFC] refactor tasklets to avoid unsigned long argument
On Mon, May 6, 2019 at 2:32 AM Allen <allen.lkml@...il.com> wrote:
> I have been toying with the idea of "refactor tasklets to avoid
> unsigned long argument" since Kees listed on KSPP wiki. I wanted to
> and have kept the implementation very simple. Let me know what you
> guys think.
>
> Note: I haven't really done much of testing besides boot testing with small
> set of files moved to the new api.
>
> My only concern with the implementation is, in the kernel the combination
> of tasklet_init/DECLARE_TAKSLET is seen in over ~400 plus files.
> With the change(dropping unsigned long argument) there will be huge list
> of patches migrating to the new api.
Yeah, this is the main part of the work for making this change. When
the timer API got changed, I had to do a two-stage change so we could
convert the users incrementally, and then finalize the API change to
drop the old style.
Beyond that, yeah, everything you sent looks good. It's just the
matter of building a series of patches to do it without breaking the
world. (Though if it's small enough, maybe it could be a single patch?
But I doubt that would be doable...)
--
Kees Cook
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
