public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31248] New: debuginfod_find_* may return fd with file-offset at end
Date: Tue, 16 Jan 2024 01:39:26 +0000	[thread overview]
Message-ID: <bug-31248-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31248

            Bug ID: 31248
           Summary: debuginfod_find_* may return fd with file-offset at
                    end
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

During the srcfiles test case diagnosis, studying the reason for occasional
0-length files, found something funky about the debuginfod_find_FOO api.

It appears possible for first-time-downloaded files to result in FDs that were
freshly written into by curl, with the file offset positioned right at the end.
 We should lseek(2) to the front.  Clients would expect to be able to read it,
as opposed to an insta-EOF.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-01-16  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  1:39 fche at redhat dot com [this message]
2024-01-16 12:47 ` [Bug debuginfod/31248] " mark at klomp dot org
2024-01-16 21:47 ` fche at redhat dot com

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-31248-10460@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).