Re: fanotify bug on gdb -- hard crash

From: ivo welch
Date: Fri Dec 26 2014 - 18:49:17 EST

hi pavel---I do a complete fresh install on ubuntu 64-bit 14.10 in a
vmware virtual machine. the gcc version is 4.9.1. this way I cannot
have made a mistake. ;-)

the compile is gcc -g -o testfa testfa.c .

the gdb and program must run with root privilege. without it, it will
just abort on the fd test.

then gdb, do "b main", "run", and step through with 'n's. you should
see "calling fanotify_mark: fd=3" and then, on the next 'n', it should
never return from the fanotify_mark. you should not be able to
interrupt. at this point, you have to pull the plug.

(I think I also trigger this sometimes without gdb, but then it is not
intermittent but replicable. I started debugging because of this

Ivo Welch (ivo.welch@xxxxxxxxx)
J. Fred Weston Professor of Finance
Anderson School at UCLA, C519
Director, UCLA Anderson Fink Center for Finance and Investments
Free Finance Textbook,
Editor, Critical Finance Review,

On Sat, Dec 27, 2014 at 6:14 AM, Pavel Machek <pavel@xxxxxx> wrote:
> On Fri 2014-12-26 22:45:38, ivo welch wrote:
>> I am not a kernel developer, so forgive the intrusion.
> Good bug reports are always welcome.
>> I suspect I have found either a bug in gdb (less likely) or a bug in
>> fanotify (more likely). it is replicable, and the code is almost
>> unchanged from the example in the fanotify man page. to trigger it,
>> all an su needs to do is to step through the program below with gdb
>> 7.8.1 'n' command, and linux locks up the system pretty hard (reboot
> Hard lockup -> this can't be gdb problem.
>> required). I have confirmed the replicability of this issue on a
>> clean arch 2014.12.01 3.17.6-1 system and on a clean ubuntu 14.10
>> system, both VMs created just to check it. /iaw
> Does it need root priviledges to trigger?
> Best regards,
> Pavel
> --
> (english)
> (cesky, pictures)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at