From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Aleksa Sarai <cyphar@cyphar.com>,
Chris Palmer <palmer@google.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Christoph Hellwig <hch@lst.de>, Matt Denton <mpdenton@google.com>,
Robert Sesek <rsesek@google.com>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
Sargun Dhillon <sargun@sargun.me>, Shuah Khan <shuah@kernel.org>,
Tycho Andersen <tycho@tycho.ws>, Will Deacon <will@kernel.org>,
Will Drewry <wad@chromium.org>, Yonghong Song <yhs@fb.com>
Subject: wine fails to start with seccomp updates for v5.9-rc1
Date: Fri, 07 Aug 2020 11:19:09 -0400 [thread overview]
Message-ID: <1596812929.lz7fuo8r2w.none@localhost> (raw)
In-Reply-To: 1596812929.lz7fuo8r2w.none.ref@localhost
Hi,
On Linus' master, wine fails to start with the following error:
wine client error:0: write: Bad file descriptor
This issue is not present on 5.8. It appears to be caused by failure to
write to a pipe FD received via SCM_RIGHTS. Therefore, I tried reverting
9ecc6ea491f0, which resolved the issue.
Thanks,
Alex.
next parent reply other threads:[~2020-08-07 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1596812929.lz7fuo8r2w.none.ref@localhost>
2020-08-07 15:19 ` Alex Xu (Hello71) [this message]
2020-08-07 15:48 ` wine fails to start with seccomp updates for v5.9-rc1 Linus Torvalds
2020-08-07 17:36 ` Thadeu Lima de Souza Cascardo
2020-08-07 17:42 ` Kees Cook
2020-08-07 17:51 ` Alex Xu (Hello71)
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=1596812929.lz7fuo8r2w.none@localhost \
--to=alex_y_xu@yahoo.ca \
--cc=cascardo@canonical.com \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=hch@lst.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdenton@google.com \
--cc=palmer@google.com \
--cc=rsesek@google.com \
--cc=sargun@sargun.me \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tycho@tycho.ws \
--cc=wad@chromium.org \
--cc=will@kernel.org \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.