On Fri, Sep 23, 2022 at 11:38:03AM +0200, Jan Kara wrote: > On Fri 23-09-22 12:10:12, Dave Chinner wrote: > > On Thu, Sep 22, 2022 at 05:41:08PM -0700, Dan Williams wrote: > > > Dave Chinner wrote: > > > > On Wed, Sep 21, 2022 at 07:28:51PM -0300, Jason Gunthorpe wrote: > > > > > On Thu, Sep 22, 2022 at 08:14:16AM +1000, Dave Chinner wrote: > > > > > > > > > > > Where are these DAX page pins that don't require the pin holder to > > > > > > also hold active references to the filesystem objects coming from? > > > > > > > > > > O_DIRECT and things like it. > > > > > > > > O_DIRECT IO to a file holds a reference to a struct file which holds > > > > an active reference to the struct inode. Hence you can't reclaim an > > > > inode while an O_DIRECT IO is in progress to it. > > > > > > > > Similarly, file-backed pages pinned from user vmas have the inode > > > > pinned by the VMA having a reference to the struct file passed to > > > > them when they are instantiated. Hence anything using mmap() to pin > > > > file-backed pages (i.e. applications using FSDAX access from > > > > userspace) should also have a reference to the inode that prevents > > > > the inode from being reclaimed. > > > > > > > > So I'm at a loss to understand what "things like it" might actually > > > > mean. Can you actually describe a situation where we actually permit > > > > (even temporarily) these use-after-free scenarios? > > > > > > Jason mentioned a scenario here: > > > > > > https://lore.kernel.org/all/YyuoE8BgImRXVkkO@xxxxxxxxxx/ > > > > > > Multi-thread process where thread1 does open(O_DIRECT)+mmap()+read() and > > > thread2 does memunmap()+close() while the read() is inflight. > > > > And, ah, what production application does this and expects to be > > able to process the result of the read() operation without getting a > > SEGV? > > > > There's a huge difference between an unlikely scenario which we need > > to work (such as O_DIRECT IO to/from a mmap() buffer at a different > > offset on the same file) and this sort of scenario where even if we > > handle it correctly, the application can't do anything with the > > result and will crash immediately.... > > I'm not sure I fully follow what we are concerned about here. As you've > written above direct IO holds reference to the inode until it is completed > (through kiocb->file->inode chain). So direct IO should be safe? AFAICT, it's the user buffer allocated by mmap() that the direct IO is DMAing into/out of that is the issue here. i.e. mmap() a file that is DAX enabled, pass the mmap region to DIO on a non-dax file, GUP in the DIO path takes a page pin on user pages that are DAX mapped, the userspace application then unmaps the file pages and unlinks the FSDAX file. At this point the FSDAX mapped inode has no active references, so the filesystem frees the inode and it's allocated storage space, and now the DIO or whatever is holding the GUP reference is now a moving storage UAF violation. What ever is holding the GUP reference doesn't even have a reference to the FSDAX filesystem - the DIO fd could point to a file in a different filesystem altogether - and so the fsdax filesytem could be unmounted at this point whilst the application is still actively using the storage underlying the filesystem. That's just .... broken. > I'd be more worried about stuff like vmsplice() that can add file pages > into pipe without holding inode alive in any way and keeping them there for > arbitrarily long time. Didn't we want to add FOLL_LONGTERM to gup executed > from vmsplice() to avoid issues like this? Yes, ISTR that was part of the plan - use FOLL_LONGTERM to ensure FSDAX can't run operations that pin pages but don't take fs references. I think that's how we prevented RDMA users from pinning FSDAX direct mapped storage media in this way. It does not, however, prevent the above "short term" GUP UAF situation from occurring. > > > Sounds plausible to me, but I have not tried to trigger it with a focus > > > test. > > > > If there really are applications this .... broken, then it's not the > > responsibility of the filesystem to paper over the low level page > > reference tracking issues that cause it. > > > > i.e. The underlying problem here is that memunmap() frees the VMA > > while there are still active task-based references to the pages in > > that VMA. IOWs, the VMA should not be torn down until the O_DIRECT > > read has released all the references to the pages mapped into the > > task address space. > > > > This just doesn't seem like an issue that we should be trying to fix > > by adding band-aids to the inode life-cycle management. > > I agree that freeing VMA while there are pinned pages is ... inconvenient. > But that is just how gup works since the beginning - the moment you have > struct page reference, you completely forget about the mapping you've used > to get to the page. So anything can happen with the mapping after that > moment. And in case of pages mapped by multiple processes I can easily see > that one of the processes decides to unmap the page (and it may well be > that was the initial process that acquired page references) while others > still keep accessing the page using page references stored in some internal > structure (RDMA anyone?). Yup, and this is why RDMA on FSDAX using this method of pinning pages will end up corrupting data and filesystems, hence FOLL_LONGTERM protecting against most of these situations from even arising. But that's that workaround, not a long term solution that allows RDMA to be run on FSDAX managed storage media. I said on #xfs a few days ago: [23/9/22 10:23] * dchinner is getting deja vu over this latest round of "dax mappings don't pin the filesystem objects that own the storage media being mapped" And I'm getting that feeling again right now... > I think it will be rather difficult to come up > with some scheme keeping VMA alive while there are pages pinned without > regressing userspace which over the years became very much tailored to the > peculiar gup behavior. Perhaps all we should do is add a page flag for fsdax mapped pages that says GUP must pin the VMA, so only mapped pages that fall into this category take the perf penalty of VMA management. > I can imagine we would keep *inode* referenced while there are its pages > pinned. We can do that by pinning the VMA, yes? > That should not be that difficult but at least in naive > implementation that would put rather heavy stress on inode refcount under > some loads so I don't think that's useful either. Having the workaround be sub-optimal for high performance workloads is a good way of discouraging applications from doing fundamentally broken crap without actually breaking anything.... -Dave. -- Dave Chinner david@xxxxxxxxxxxxx
