On Fri, Nov 22, 2019 at 10:05 PM Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > > On Sat, Nov 23, 2019 at 05:35:14AM +0000, Al Viro wrote: > > On Fri, Nov 22, 2019 at 09:19:21PM -0800, Alexei Starovoitov wrote: > > > > > hard to tell. It will be run out of bpf prog that attaches to kprobe or > > > tracepoint. What is the concern about locking? > > > d_path() doesn't take any locks and doesn't depend on any locks. Above 'if' > > > checks that plain d_path() is used and not some specilized callback with > > > unknown logic. > > > > It sure as hell does. It might end up taking rename_lock and/or mount_lock > > spinlock components. It'll try not to, but if the first pass ends up with > > seqlock mismatch, it will just grab the spinlock the second time around. > > ohh. got it. I missed _or_lock() part in there. > The need_seqretry() logic is tricky. afaics there is no way for the checks > outside of prepend_path() to prevent spin_lock to happen. And adding a flag to > prepend_path() to return early if retry is needed is too ugly. So this helper > won't be safe to be run out of kprobe. But if we allow it for tracepoints only > it should be ok. I think. There are no tracepoints in inner guts of vfs and I > don't think they will ever be. So running in tracepoint->bpf_prog->d_path we > will be sure that rename_lock+mount_lock can be safely spinlocked. Am I missing > something? It seems rather restrictive to only allow tracepoints (especially without VFS tracepoints), although I'll use it to improve my syscall tracepoint tools, so I'd be happy to see this merged even with that restriction. Just a thought: if *buffer is in BPF memory, can prepend_path() check it's memory location and not try to grab the lock based on that? This would be to avoid adding a flag. > > > > > with this number; quite possibly never before that function had been called > > > > _and_ not once after it has returned. > > > > > > Right. TOCTOU is not a concern here. It's tracing. It's ok for full path to be > > > 'one time deal'. > > > > It might very well be a full path of something completely unrelated to what > > the syscall ends up operating upon. It's not that the file might've been > > moved; it might be a different file. IOW, results of that tracing might be > > misleading. > > That is correct. Tracing is fine with such limitation. Still better than probe_read. > +1 Tracing is observability tools and we document these caveats, and this won't be the first time I've published tools where the printed path may not be the one you think (e.g., the case of hard links.) Brendan -- Brendan Gregg, Senior Performance Architect, Netflix
