From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH 0/7] Btrfs: bugs found by sparse and RCU strings
Date: Tue, 22 Aug 2017 23:45:58 -0700 [thread overview]
Message-ID: <cover.1503470354.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
I came across my ancient RCU string branch [1] and decided to revive it
and finally put it to rest. In the process of checking it with sparse, I
found a handful of other issues.
Patch 1 should probably go in 4.13, as it fixes bugs introduced this
cycle by the conversion to blk_status_t. Patch 2 is an old bug, so it
could wait for 4.14 but it might as well go in for 4.13. Patches 3-5 are
the RCU string series. Patches 6 and 7 are minor cleanups found by
sparse. Patches 3-7 can wait for 4.14 or 4.15.
Based on 4.13-rc6.
Thanks!
1: https://lwn.net/Articles/629048/
Omar Sandoval (7):
Btrfs: fix blk_status_t/errno confusion
Btrfs: fix incorrect {node,sector}size endianness from
BTRFS_IOC_FS_INFO
Move Btrfs RCU string to common library
Btrfs: refactor btrfs_device->name updates
Btrfs: fix suspicious RCU in BTRFS_IOC_DEV_INFO
Btrfs: make some volumes.c functions static
Btrfs: fix __user casting in ioctl.c
fs/btrfs/check-integrity.c | 12 +--
fs/btrfs/dev-replace.c | 37 +++++----
fs/btrfs/disk-io.c | 10 +--
fs/btrfs/extent_io.c | 8 +-
fs/btrfs/inode.c | 70 ++++++++--------
fs/btrfs/ioctl.c | 30 +++----
fs/btrfs/raid56.c | 35 ++++----
fs/btrfs/rcu-string.h | 56 -------------
fs/btrfs/scrub.c | 42 +++++-----
fs/btrfs/super.c | 7 +-
fs/btrfs/volumes.c | 199 +++++++++++++++++++++++++++------------------
fs/btrfs/volumes.h | 8 +-
include/linux/rcustring.h | 97 ++++++++++++++++++++++
13 files changed, 351 insertions(+), 260 deletions(-)
delete mode 100644 fs/btrfs/rcu-string.h
create mode 100644 include/linux/rcustring.h
--
2.14.1
next reply other threads:[~2017-08-23 6:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 6:45 Omar Sandoval [this message]
2017-08-23 6:45 ` [PATCH 1/7] Btrfs: fix blk_status_t/errno confusion Omar Sandoval
2017-08-23 15:50 ` David Sterba
2017-08-23 16:13 ` Liu Bo
2017-08-23 19:18 ` Omar Sandoval
2017-08-23 6:46 ` [PATCH 2/7] Btrfs: fix incorrect {node,sector}size endianness from BTRFS_IOC_FS_INFO Omar Sandoval
2017-09-06 14:51 ` David Sterba
2017-08-23 6:46 ` [PATCH 3/7] Move Btrfs RCU string to common library Omar Sandoval
2017-09-06 15:15 ` David Sterba
2017-09-07 17:10 ` Omar Sandoval
2017-08-23 6:46 ` [PATCH 4/7] Btrfs: refactor btrfs_device->name updates Omar Sandoval
2017-08-23 6:46 ` [PATCH 5/7] Btrfs: fix suspicious RCU in BTRFS_IOC_DEV_INFO Omar Sandoval
2017-09-06 15:37 ` David Sterba
2017-09-07 17:24 ` Omar Sandoval
2017-08-23 6:46 ` [PATCH 6/7] Btrfs: make some volumes.c functions static Omar Sandoval
2017-09-06 15:25 ` David Sterba
2017-08-23 6:46 ` [PATCH 7/7] Btrfs: fix __user casting in ioctl.c Omar Sandoval
2017-09-06 15:23 ` David Sterba
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=cover.1503470354.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.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).