From: Xi Ruoyao <xry111@xry111.site>
To: abush wang <abushwangs@gmail.com>, Florian Weimer <fweimer@redhat.com>
Cc: abushwang via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] nptl: pthread_rwlock_rdlock return in low priority
Date: Tue, 07 Mar 2023 17:57:19 +0800 [thread overview]
Message-ID: <fcc0514d38c23d7fdbad6cd234411442ef7cb31a.camel@xry111.site> (raw)
In-Reply-To: <CAMLoAPaDiqTOcG=HZoyMzevuttUqXUvdmd8ik68iSq20C1f-vg@mail.gmail.com>
On Tue, 2023-03-07 at 17:06 +0800, abush wang via Libc-alpha wrote:
> Actually, i can not send mail without any change by git sendmail, so I
> add
> a empty line.
> This is just a mail for advisory
Don't use git send-email then. It's a utility to send patches as mails,
not ordinary mails.
If you need a CLI tool for email use sendmail or something.
>
> Florian Weimer <fweimer@redhat.com> 于2023年3月7日周二 16:56写道:
>
> > * abushwang via Libc-alpha:
> >
> > > diff --git a/nptl/pthread_rwlock_common.c
> > > b/nptl/pthread_rwlock_common.c
> > > index 5266a00ed1..35b00fc14f 100644
> > > --- a/nptl/pthread_rwlock_common.c
> > > +++ b/nptl/pthread_rwlock_common.c
> > > @@ -389,6 +389,7 @@ __pthread_rwlock_rdlock_full64
> > > (pthread_rwlock_t
> > *rwlock, clockid_t clockid,
> > > complexity. */
> > > if (__glibc_likely ((r & PTHREAD_RWLOCK_WRPHASE) == 0))
> > > return 0;
> > > +
> > > /* Otherwise, if we were in a write phase (states #6 or #8), we
> > > must
> > wait
> > > for explicit hand-over of the read phase; the only exception
> > > is if
> > we
> > > can start a read phase if there is no primary writer
> > > currently. */
> >
> > This does not seem to be the right patch?
> >
> > Thanks,
> > Florian
> >
> >
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2023-03-07 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 3:50 abushwang
2023-03-07 8:40 ` Xi Ruoyao
2023-03-07 8:53 ` abush wang
2023-03-07 8:56 ` Florian Weimer
2023-03-07 9:06 ` abush wang
2023-03-07 9:57 ` Xi Ruoyao [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=fcc0514d38c23d7fdbad6cd234411442ef7cb31a.camel@xry111.site \
--to=xry111@xry111.site \
--cc=abushwangs@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).