From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/pread02: extend buffer to avoid glibc overflow detection
Date: Mon, 31 Jan 2022 13:44:21 +0100 [thread overview]
Message-ID: <YffZpWqHOhBixYbW@pevik> (raw)
In-Reply-To: <0e15e1df7251384368ae363cc4f19528d0e77a39.1643627166.git.jstancek@redhat.com>
Hi Jan,
> Test started failing with recent glibc (glibc-2.34.9000-38.fc36),
> which detects that buffer in pread is potentially too small:
> tst_test.c:1431: TINFO: Timeout per run is 0h 05m 00s
> *** buffer overflow detected ***: terminated
> tst_test.c:1484: TBROK: Test killed by SIGIOT/SIGABRT!
> (gdb) bt
> #0 __pthread_kill_implementation at pthread_kill.c:44
> #1 0x00007ffff7e46f73 in __pthread_kill_internal at pthread_kill.c:78
> #2 0x00007ffff7df6a36 in __GI_raise at ../sysdeps/posix/raise.c:26
> #3 0x00007ffff7de082f in __GI_abort () at abort.c:79
> #4 0x00007ffff7e3b01e in __libc_message at ../sysdeps/posix/libc_fatal.c:155
> #5 0x00007ffff7ed945a in __GI___fortify_fail at fortify_fail.c:26
> #6 0x00007ffff7ed7dc6 in __GI___chk_fail () at chk_fail.c:28
> #7 0x00007ffff7ed8214 in __pread_chk at pread_chk.c:26
> #8 0x0000000000404d1a in pread at /usr/include/bits/unistd.h:74
> #9 verify_pread (n=<optimized out>) at pread02.c:44
> #10 0x000000000040dc19 in run_tests () at tst_test.c:1246
> #11 testrun () at tst_test.c:1331
> #12 fork_testrun () at tst_test.c:1462
> #13 0x000000000040e9a1 in tst_run_tcases
> #14 0x0000000000404bde in main
> Extend it to number of bytes we are trying to read from fd.
LGTM.
Acked-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-31 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 11:06 [LTP] [PATCH] syscalls/pread02: extend buffer to avoid glibc overflow detection Jan Stancek
2022-01-31 12:44 ` Petr Vorel [this message]
2022-01-31 16:25 ` Cyril Hrubis
2022-02-01 7:00 ` Jan Stancek
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=YffZpWqHOhBixYbW@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox