Re: [PATCH bpf-next 1/2] bpf: add bpf_init_inode_xattr kfunc for atomic inode labeling
David Windsor <[email protected]>
| Newsgroups | dev.linux.lists.sashiko,org.kernel.vger.bpf |
|---|---|
| Message-ID | <CAEXv5_hCV0BGG=gDN1kupuhe=o+wCojTW32-R=9J8zmi4SR6KA@mail.gmail.com> |
On Sun, Apr 26, 2026 at 8:56 PM <[email protected]> wrote: > ... > > Can this result in a use-after-free of the name string? The name__str > argument typically resides in a BPF map. > > Since the filesystem's initxattrs callback can perform disk I/O and sleep > after the BPF hook completes, what happens if the BPF program is unloaded > and its maps are freed concurrently? > > The name pointer might then point to freed memory when the filesystem > attempts to write the xattr. > Yeah, good point. We'll kmemdup the name just as we're already doing for the value.