On 2019-11-12, Kees Cook <keescook@xxxxxxxxxxxx> wrote: > On Tue, Nov 12, 2019 at 12:24:04AM +1100, Aleksa Sarai wrote: > > On 2019-11-05, Aleksa Sarai <cyphar@xxxxxxxxxx> wrote: > > > This patchset is being developed here: > > > <https://github.com/cyphar/linux/tree/openat2/master> > > > > > > Patch changelog: > > > v15: > > > * Fix code style for LOOKUP_IN_ROOT handling in path_init(). [Linus Torvalds] > > > * Split out patches for each individual LOOKUP flag. > > > * Reword commit messages to give more background information about the > > > series, as well as mention the semantics of each flag in more detail. > > > [...] > > > > Ping -- this patch hasn't been touched for a week. Thanks. > > If I've been following correctly, everyone is happy with this series. > (i.e. Linus's comment appear to have been addressed.) > > Perhaps the next question is should this go via a pull request by you to > Linus directly during the v5.5 merge window, via akpm, via akpm, via > Christian, or some other path? Besides Linus, it's not been clear who > should "claim" this series. :) Given the namei changes, I wanted to avoid stepping on Al's toes. Though he did review the series a few versions ago, the discussion didn't focus on the openat2(2) semantics (which have also changed since then). I'm not sure whether to interpret the silence to mean he's satisfied with things as they are, or if he hasn't had more time to look at the series. As for which tree it should be routed to, I don't mind -- Christian is the most straight-forward choice (but if Al wants to route it, that's fine with me too). -- Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH <https://www.cyphar.com/>
Attachment:
signature.asc
Description: PGP signature
