From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 94791] syscall fanotify_mark overflow.
Date: Tue, 24 Nov 2015 16:14:57 +0000 [thread overview]
Message-ID: <bug-94791-13602-NJqWhmtioV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94791-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94791
Tim Pickersgill <tim.pickersgill@sophos.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tim.pickersgill@sophos.com
--- Comment #1 from Tim Pickersgill <tim.pickersgill@sophos.com> ---
A __u64 value is an unsigned long long, a 64-bit integer, regardless of system
bitness. Not sure how/why this would overflow on a 32-bit system. What symptoms
are you seeing?
We're using fanotify_mark() on 32-bit systems without seeing any issue here.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-11-24 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 9:40 [Bug 94791] New: syscall fanotify_mark overflow bugzilla-daemon
2015-11-24 16:14 ` bugzilla-daemon [this message]
2015-12-01 11:07 ` [Bug 94791] " bugzilla-daemon
2015-12-01 14:08 ` bugzilla-daemon
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=bug-94791-13602-NJqWhmtioV@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.