From: Pavel Machek <pavel@ucw.cz>
To: ivo.welch@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: fanotify bug on gdb -- hard crash
Date: Fri, 26 Dec 2014 23:14:44 +0100 [thread overview]
Message-ID: <20141226221444.GA13349@amd> (raw)
In-Reply-To: <CAPr7RtWpX_kYiJRRnPVSZrL-U2GqoV5aBPM_AF7xBzV99jzJuw@mail.gmail.com>
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) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-12-26 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 14:45 fanotify bug on gdb -- hard crash ivo welch
2014-12-26 18:40 ` Heinrich Schuchardt
2014-12-28 23:13 ` Eric Paris
[not found] ` <CAPr7RtWQ6bt4M8f-2-w0nbLvgpupb0kckE=VQDYbC8EXwiPDJg@mail.gmail.com>
2014-12-29 4:29 ` Eric Paris
2014-12-29 5:06 ` ivo welch
2014-12-31 0:21 ` Eric Paris
2014-12-26 22:14 ` Pavel Machek [this message]
2014-12-26 23:48 ` ivo welch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141226221444.GA13349@amd \
--to=pavel@ucw.cz \
--cc=ivo.welch@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.