public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/18990] fopencookie broken w.r.t seek within buffered range
Date: Thu, 01 Oct 2015 12:40:00 -0000	[thread overview]
Message-ID: <bug-18990-131-qtoKtZT1Y1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18990-131@http.sourceware.org/bugzilla/>

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
Can you provide a test case?  It is not clear to me how changing *internal*
FILE object data in this way would negatively impact the behavior of
user-supplied callbacks.

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


  reply	other threads:[~2015-10-01 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  9:36 [Bug stdio/18990] New: " luoqi.chen at gmail dot com
2015-10-01 12:40 ` fweimer at redhat dot com [this message]
2015-10-08  3:22 ` [Bug stdio/18990] " luoqi.chen at gmail dot com
2015-10-08  9:02 ` fweimer at redhat dot com
2015-10-08 19:11 ` luoqi.chen at gmail dot com
2015-10-26 23:25 ` luoqi.chen at gmail 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-18990-131-qtoKtZT1Y1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).