From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v2] Cygwin: dtable: Delete old kludge code for /dev/tty.
Date: Fri, 7 Jul 2023 11:34:17 +0200 [thread overview]
Message-ID: <ZKfcGQgQmUfb7gH5@calimero.vinschen.de> (raw)
In-Reply-To: <20230707123005.493ee21ae5ad31500af6415c@nifty.ne.jp>
On Jul 7 12:30, Takashi Yano wrote:
> Hi Corinna,
>
> On Tue, 4 Jul 2023 16:36:26 +0200
> Corinna Vinschen wrote:
> > On Jul 4 19:03, Takashi Yano wrote:
> > > This old kludge code assigns fhandler_console for /dev/tty even
> > > if the CTTY is not a console when stat() has been called. Due to
> > > this, the problem reported in
> > > https://cygwin.com/pipermail/cygwin/2023-June/253888.html
> > > occurs after the commit 3721a756b0d8 ("Cygwin: console: Make the
> > > console accessible from other terminals.").
> > >
> > > This patch fixes the issue by dropping the old kludge code.
> > >
> > > Though the exact reason why the kludge code was necessary is not
> > > clear enough, this kluge code has no longer seemed to be necessary
> > ^^^^^^^^^^^^^^^^^^^^
> > I'm not a native speaker myself, but
> >
> > no longer seems
> >
> > might be better here.
> >
> > Anyway, this is GTG.
>
> I think I understand correctly the concept of cnew_no_ctor macro in
> dtable.cc now. cnew_no_ctor calls fhandler_console(void *) instead of
> fhandler_console(fh_devices) to omits initialization of instance for
> stat() call. This might make stat() slightly faster.
>
> Based on this understanding, I would like to withdraw the previous
> patch, and propose new patch series.
>
> Could you please review the patch seriese?
Great, will do!
Thanks,
Corinna
prev parent reply other threads:[~2023-07-07 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 10:03 Takashi Yano
2023-07-04 14:36 ` Corinna Vinschen
2023-07-07 3:30 ` Takashi Yano
2023-07-07 9:34 ` Corinna Vinschen [this message]
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=ZKfcGQgQmUfb7gH5@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.com \
/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).