From: Latchesar Ionkov <lucho@ionkov.net>
To: Tuomas Tynkkynen <tuomas@tuxera.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>,
Eric Van Hensbergen <ericvh@gmail.com>,
Ron Minnich <rminnich@sandia.gov>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] 9p: Fixes for hard-to-hit bugs
Date: Thu, 7 Sep 2017 08:49:54 -0600 [thread overview]
Message-ID: <CAOha14xxn4btO3Gd=qYj-JGFHvsFqQWJGGjX8HLDRiWAL7fKTA@mail.gmail.com> (raw)
In-Reply-To: <20170906145908.8082-1-tuomas@tuxera.com>
Acked-by: Latchesar Ionkov <lucho@ionkov.net>
On Wed, Sep 6, 2017 at 8:59 AM, Tuomas Tynkkynen <tuomas@tuxera.com> wrote:
> These two patches fix two hard-to-hit (but really annoying) bugs in 9p.
> The first one was posted earlier in February (with one R-b), the second
> is a new one.
>
> Both of these have had soaking in NixOS distribution kernels for
> a couple of months with no ill effects.
>
> Tuomas Tynkkynen (2):
> fs/9p: Compare qid.path in v9fs_test_inode
> net/9p: Switch to wait_event_killable()
>
> fs/9p/vfs_inode.c | 3 +++
> fs/9p/vfs_inode_dotl.c | 3 +++
> net/9p/client.c | 3 +--
> net/9p/trans_virtio.c | 13 ++++++-------
> net/9p/trans_xen.c | 4 ++--
> 5 files changed, 15 insertions(+), 11 deletions(-)
>
> --
> 2.13.0
>
next prev parent reply other threads:[~2017-09-07 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 14:59 [PATCH 0/2] 9p: Fixes for hard-to-hit bugs Tuomas Tynkkynen
2017-09-06 14:59 ` [PATCH 1/2] fs/9p: Compare qid.path in v9fs_test_inode Tuomas Tynkkynen
2017-09-06 14:59 ` [PATCH 2/2] net/9p: Switch to wait_event_killable() Tuomas Tynkkynen
2017-09-07 14:49 ` Latchesar Ionkov [this message]
2017-09-26 13:10 ` [PATCH 0/2] 9p: Fixes for hard-to-hit bugs Tuomas Tynkkynen
2017-10-20 20:11 ` Al Viro
2017-10-24 1:41 ` Tuomas Tynkkynen
2017-10-24 2:11 ` Al Viro
2017-10-20 12:34 ` Tuomas Tynkkynen
2017-10-20 19:40 ` Linus Torvalds
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='CAOha14xxn4btO3Gd=qYj-JGFHvsFqQWJGGjX8HLDRiWAL7fKTA@mail.gmail.com' \
--to=lucho@ionkov.net \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rminnich@sandia.gov \
--cc=tuomas@tuxera.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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.