From eb19d41d5f85f169cee7570f783821cb705ad37a Mon Sep 17 00:00:00 2001 From: Dave Reisner Date: Wed, 3 Jul 2013 20:33:19 -0400 Subject: do not check error from close(2) On operating systems we support, the behavior is always such that the kernel will do the right thing as far as invalidating the file descriptor, regardless of the eventual return value. Therefore, potentially looping and calling close multiple times is wrong. At best, we call close again on an invalid FD and throw a spurious EBADF error. At worst, we might close an FD which doesn't belong to us when a multi-threaded application opens its own file descriptor between iterations of the loop. Signed-off-by: Dave Reisner Signed-off-by: Allan McRae --- lib/libalpm/be_sync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/libalpm/be_sync.c') diff --git a/lib/libalpm/be_sync.c b/lib/libalpm/be_sync.c index f9fd5d1f..feda6f5d 100644 --- a/lib/libalpm/be_sync.c +++ b/lib/libalpm/be_sync.c @@ -474,7 +474,7 @@ static int sync_db_populate(alpm_db_t *db) cleanup: _alpm_archive_read_free(archive); if(fd >= 0) { - CLOSE(fd); + close(fd); } return count; } -- cgit v1.2.3-24-g4f1b