Netdev List
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: v9fs-developer@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [GIT PULL] 9p updates for 4.21
Date: Wed, 2 Jan 2019 04:54:39 +0100	[thread overview]
Message-ID: <20190102035439.GA30733@nautica> (raw)

Small pull request this time around with only two commits; some missing
prototype warning fix and a syzkaller fix when a 9p server advertises a
too small msize.

The commit date is close-ish because I reworded a commit message to
add a Cc to stable for the msize fix recently, but the patchs themselves
have been in linux-next since Nov 20~ish


Thanks,

The following changes since commit ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:

  Linux 4.20-rc2 (2018-11-11 17:12:31 -0600)

are available in the Git repository at:

  git://github.com/martinetd/linux tags/9p-for-4.21

for you to fetch changes up to 574d356b7a02c7e1b01a1d9cba8a26b3c2888f45:

  9p/net: put a lower bound on msize (2018-12-25 17:07:49 +0900)

----------------------------------------------------------------
Pull request for inclusion in 4.21

Missing prototype warning fix and a syzkaller fix when a 9p server
advertises a too small msize

----------------------------------------------------------------
Adeodato Simó (1):
      net/9p: include trans_common.h to fix missing prototype warning.

Dominique Martinet (1):
      9p/net: put a lower bound on msize

 net/9p/client.c       | 21 +++++++++++++++++++++
 net/9p/trans_common.c |  1 +

-- 
Dominique Martinet

             reply	other threads:[~2019-01-02  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02  3:54 Dominique Martinet [this message]
2019-01-02 20:15 ` [GIT PULL] 9p updates for 4.21 pr-tracker-bot

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=20190102035439.GA30733@nautica \
    --to=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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