On Tue, Jun 17, 2025 at 2:53 PM Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Jun 17, 2025 at 10:31:37AM -0700, Alexei Starovoitov wrote: > > On Sat, Jun 14, 2025 at 5:47 PM Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > > > > > > [don't really care which tree that goes through; right now it's > > > in viro/vfs.git #work.misc, but if somebody prefers to grab it > > > through a different tree, just say so] > > > always equal to __get_seq_info(2nd argument) > > > > We'll take it through bpf-next, > > but it needs a proper commit log that explains the motivation. > > Just to clean up the code a bit ? > > or something else? > > Umm... It had been sitting around for a couple of years, but IIRC > that was from doing data flow analysis for bpf_iter_seq_info. > I really don't remember details of that code audit, so just chalk > it up to cleaning the code up a bit. Applied to bpf-next.
