From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] readdir02: use invalid DIR stream descriptor
Date: Mon, 28 Jan 2019 16:16:23 +0100 [thread overview]
Message-ID: <20190128151622.GA10646@rei.lan> (raw)
In-Reply-To: <20181220090811.21514-2-liwang@redhat.com>
Hi!
> Issue:
> On ppc64le and aarch64, when testing in NFS mountpoint, test
> process receives SIGSEGV when calling readdir on a DIR which
> has just been closed by closedir().
>
> Unfortunately, ltp/readdir02.c handles SIGSEGV. This makes it
> hits SIGSEGV again in its cleanup function. So readdir02 hangs
> there hitting SEGV endlessly.
>
> That's because a DIR * is NOT a file descriptor. It's memory
> allocated by opendir() that contains libc internal information
> about the directory. closedir(test_dir) frees any memory associated
> with the open directory pointer test_dir.
>
> To then pass the freed dir pointer to readdir() is a use-after-free.
> It probably won't return EBADF, it will dereference freed memory
> and whatever happens after that is undefined.
>
> In this patch, I simply modify the test to use an exist FILE *
> stream to simulate the invalid directory stream descriptor. Then
> it won't hit the use-after-free issue any more.
Actually I think that the best we can do here is to delete the testcase
because:
* Casting FILE* to DIR* is IMHO invoking even worse undefined behavior
than the original test that called readdir() on closed DIR*
* We do cover the EBADF for getents() syscalls getents02 test
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-01-28 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 9:08 [LTP] [PATCH 1/2] readdir: rewrite readdir02 Li Wang
2018-12-20 9:08 ` [LTP] [PATCH 2/2] readdir02: use invalid DIR stream descriptor Li Wang
2019-01-28 15:16 ` Cyril Hrubis [this message]
2019-02-01 6:59 ` Li Wang
2019-02-07 12:51 ` Cyril Hrubis
2019-02-15 8:40 ` Li Wang
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=20190128151622.GA10646@rei.lan \
--to=chrubis@suse.cz \
--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