From: Luis Chamberlain <mcgrof@kernel•org>
To: Tetsuo Handa <penguin-kernel@i-love•sakura.ne.jp>
Cc: David Howells <dhowells@redhat•com>,
Christian Borntraeger <borntraeger@de•ibm.com>,
Christoph Hellwig <hch@infradead•org>,
"Eric W. Biederman" <ebiederm@xmission•com>,
ast@kernel•org, axboe@kernel•dk, bfields@fieldses•org,
bridge@lists•linux-foundation.org, chainsaw@gentoo•org,
christian.brauner@ubuntu•com, chuck.lever@oracle•com,
davem@davemloft•net, gregkh@linuxfoundation•org,
jarkko.sakkinen@linux•intel.com, jmorris@namei•org,
josh@joshtriplett•org, keescook@chromium•org,
keyrings@vger•kernel.org, kuba@kernel•org,
lars.ellenberg@linbit•com, linux-fsdevel@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-nfs@vger•kernel.org,
linux-security-module@vger•kernel.org,
nikolay@cumulusnetworks•com, philipp.reisner@linbit•com,
ravenexp@gmail•com, roopa@cumulusnetworks•com, serge@hallyn•com,
slyfox@gentoo•org, viro@zeniv•linux.org.uk,
yangtiezhu@loongson•cn, netdev@vger•kernel.org,
markward@linux•ibm.com, linux-s390 <linux-s390@vger•kernel.org>
Subject: Re: linux-next: umh: fix processed error when UMH_WAIT_PROC is used seems to break linux bridge on s390x (bisected)
Date: Fri, 3 Jul 2020 13:28:50 +0000 [thread overview]
Message-ID: <20200703132850.GW4332@42.do-not-panic.com> (raw)
In-Reply-To: <d8a74a06-de97-54ae-de03-0d955e82f62b@i-love.sakura.ne.jp>
On Fri, Jul 03, 2020 at 09:52:01AM +0900, Tetsuo Handa wrote:
> On 2020/07/03 4:46, Luis Chamberlain wrote:
> > The alternative to making a compromise is using generic wrappers for
> > things which make sense and letting the callers use those.
>
> I suggest just introducing KWIFEXITED()/KWEXITSTATUS()/KWIFSIGNALED()/KWTERMSIG()
> macros and fixing the callers, for some callers are not aware of possibility of
> KWIFSIGNALED() case.
OK so we open code all uses. Do that in a next iteration.
Luis
next prev parent reply other threads:[~2020-07-03 13:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200610154923.27510-5-mcgrof@kernel.org>
2020-06-23 14:11 ` linux-next: umh: fix processed error when UMH_WAIT_PROC is used seems to break linux bridge on s390x (bisected) Christian Borntraeger
2020-06-23 14:23 ` Christian Borntraeger
2020-06-24 11:11 ` Christian Borntraeger
2020-06-24 12:05 ` Luis Chamberlain
2020-06-24 13:17 ` Luis Chamberlain
2020-06-24 16:13 ` Luis Chamberlain
2020-06-24 14:43 ` Christoph Hellwig
2020-06-24 15:54 ` Christian Borntraeger
2020-06-24 16:09 ` Luis Chamberlain
2020-06-24 17:58 ` Christian Borntraeger
2020-06-24 18:09 ` Christian Borntraeger
2020-06-24 18:32 ` Christian Borntraeger
2020-06-24 18:37 ` Christian Borntraeger
2020-06-25 13:26 ` Christian Borntraeger
2020-06-26 2:54 ` Luis Chamberlain
2020-06-26 5:22 ` Christian Borntraeger
2020-06-26 9:00 ` Christoph Hellwig
2020-06-26 11:40 ` Luis Chamberlain
2020-06-26 11:50 ` Luis Chamberlain
2020-06-30 17:57 ` Luis Chamberlain
2020-07-01 10:08 ` Christian Borntraeger
2020-07-01 13:24 ` Tetsuo Handa
2020-07-01 13:53 ` Luis Chamberlain
2020-07-01 14:08 ` Tetsuo Handa
2020-07-01 15:38 ` Luis Chamberlain
2020-07-01 15:48 ` Christian Borntraeger
2020-07-01 15:58 ` Luis Chamberlain
2020-07-01 16:01 ` Christian Borntraeger
2020-07-02 4:26 ` Tetsuo Handa
2020-07-02 19:46 ` Luis Chamberlain
2020-07-03 0:52 ` Tetsuo Handa
2020-07-03 13:28 ` Luis Chamberlain [this message]
2020-07-01 15:26 ` Christian Borntraeger
2020-07-01 13:46 ` Luis Chamberlain
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=20200703132850.GW4332@42.do-not-panic.com \
--to=mcgrof@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=axboe@kernel$(echo .)dk \
--cc=bfields@fieldses$(echo .)org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=chainsaw@gentoo$(echo .)org \
--cc=christian.brauner@ubuntu$(echo .)com \
--cc=chuck.lever@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=hch@infradead$(echo .)org \
--cc=jarkko.sakkinen@linux$(echo .)intel.com \
--cc=jmorris@namei$(echo .)org \
--cc=josh@joshtriplett$(echo .)org \
--cc=keescook@chromium$(echo .)org \
--cc=keyrings@vger$(echo .)kernel.org \
--cc=kuba@kernel$(echo .)org \
--cc=lars.ellenberg@linbit$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-nfs@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=markward@linux$(echo .)ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nikolay@cumulusnetworks$(echo .)com \
--cc=penguin-kernel@i-love$(echo .)sakura.ne.jp \
--cc=philipp.reisner@linbit$(echo .)com \
--cc=ravenexp@gmail$(echo .)com \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=serge@hallyn$(echo .)com \
--cc=slyfox@gentoo$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=yangtiezhu@loongson$(echo .)cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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