Thanks for Jeff's reply. I did see ERESTARTSYS in userland. As described in the above "Reproduction" chapter, "dd" fails with "dd: error writing '/mnt/test1/1G': Unknown error 512". After strace "dd", it turns out that syscall WRITE fails with: write(1, "4\303\31\211\316\237\333\r-\275g\370\233\374X\277\374Tb\202\24\365\220\320\16\27o3\331q\344\364"..., 1048576) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) In fact, other syscalls related to file systems can also fail with ERESTARTSYS in our cases, for example: mount, open, read, write and so on. Maybe the reason is that on forced unmount, rpc_killall_tasks() in net/sunrpc/clnt.c will set all inflight IO with ERESTARTSYS, while no signal gets involved. So ERESTARTSYS is not handled before entering userspace. Best regards, Zhitao Li at SmartX. On Thu, Feb 22, 2024 at 7:05 PM Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > On Wed, 2024-02-21 at 13:48 +0000, Trond Myklebust wrote: > > On Wed, 2024-02-21 at 16:20 +0800, Zhitao Li wrote: > > > [You don't often get email from zhitao.li@xxxxxxxxxx. Learn why this > > > is important at https://aka.ms/LearnAboutSenderIdentification ] > > > > > > Hi, everyone, > > > > > > - Facts: > > > I have a remote NFS export and I mount the same export on two > > > different directories in my OS with the same options. There is an > > > inflight IO under one mounted directory. And then I unmount another > > > mounted directory with force. The inflight IO ends up with "Unknown > > > error 512", which is ERESTARTSYS. > > > > > > > All of the above is well known. That's because forced umount affects > > the entire filesystem. Why are you using it here in the first place? It > > is not intended for casual use. > > > > While I agree Trond's above statement, the kernel is not supposed to > leak error codes that high into userland. Are you seeing ERESTARTSYS > being returned to system calls? If so, which ones? > -- > Jeff Layton <jlayton@xxxxxxxxxx>
