linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	david@fromorbit.com, linux-kernel@vger.kernel.org,
	sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: cleanups for 5.3-rc3
Date: Sat, 3 Aug 2019 09:33:12 -0700	[thread overview]
Message-ID: <20190803163312.GK7138@magnolia> (raw)

Hi Linus,

Here are a couple more bug fixes that trickled in since -rc1.  It's
survived the usual xfstests runs and merges cleanly with this morning's
master.  Please let me know if anything strange happens.

--D

The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:

  Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.3-fixes-1

for you to fetch changes up to afa1d96d1430c2138c545fb76e6dcb21222098d4:

  xfs: Fix possible null-pointer dereferences in xchk_da_btree_block_check_sibling() (2019-07-30 11:28:20 -0700)

----------------------------------------------------------------
Changes since last update:
- Avoid leaking kernel stack contents to userspace.
- Fix a potential null pointer dereference in the dabtree scrub code.

----------------------------------------------------------------
Darrick J. Wong (1):
      xfs: fix stack contents leakage in the v1 inumber ioctls

Jia-Ju Bai (1):
      xfs: Fix possible null-pointer dereferences in xchk_da_btree_block_check_sibling()

 fs/xfs/scrub/dabtree.c | 6 +++++-
 fs/xfs/xfs_itable.c    | 3 +++
 2 files changed, 8 insertions(+), 1 deletion(-)

             reply	other threads:[~2019-08-03 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 16:33 Darrick J. Wong [this message]
2019-08-03 17:46 ` [GIT PULL] xfs: cleanups for 5.3-rc3 Linus Torvalds
2019-08-03 21:07   ` Darrick J. Wong
2019-08-03 18:25 ` 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=20190803163312.GK7138@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).