public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [GIT PULL] brown paper bag fix for SIGPOLL si_codes
Date: Tue, 19 Sep 2017 18:13:00 -0500	[thread overview]
Message-ID: <87shfi2sg3.fsf@xmission.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709191605370.31866@macbook-air> (Vince Weaver's message of "Tue, 19 Sep 2017 16:06:49 -0400 (EDT)")

Vince Weaver <vincent.weaver@maine.edu> writes:

> On Tue, 19 Sep 2017, Eric W. Biederman wrote:
>
>> When sorting out the si_code ambiguity fcntl I accidentally overshot and
>> included SIGPOLL as well.  Ooops!  This is my trivial fix for that.
>> 
>> Vince Weaver caught this when it landed in your tree with his
>> perf_event_tests many of which started failing because the si_code changed.
>
> I've tested with this patch applied and can confirm all of my tests now 
> pass again.

And in my tiredness and distractedness doing this on my honeymoon
I forgot to include:

Fixes: d08477aa975e ("fcntl: Don't use ambiguous SIG_POLL si_codes")

Not that there are any backport issues since all of this is new with
-rc1.  But just in case someone needs the information for double
checking me.

Eric

      reply	other threads:[~2017-09-19 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 18:30 [GIT PULL] brown paper bag fix for SIGPOLL si_codes Eric W. Biederman
2017-09-19 20:06 ` Vince Weaver
2017-09-19 23:13   ` Eric W. Biederman [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=87shfi2sg3.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.weaver@maine.edu \
    /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