Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zfs-0.7.7 patchset (squashed) #7278

Conversation

tonyhutter
Copy link
Contributor

@tonyhutter tonyhutter commented Mar 7, 2018

Description

This is a squashed patchset for zfs-0.7.7. The individual commits are in the tonyhutter:zfs-0.7.7-hutter branch. I squashed the commits so that buildbot wouldn't have to run against each one, and because github/buillbot seem to have a maximum limit of 30 commits they can test in a PR.

Motivation and Context

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (a change to man pages or other documentation)

Checklist:

  • My code follows the ZFS on Linux code style requirements.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commit messages are properly formatted and contain Signed-off-by.
  • Change has been approved by a ZFS on Linux member.

@loli10K
Copy link
Contributor

loli10K commented Mar 8, 2018

I'm worried that including #6963 (and #7074) in 0.7.x might break some Debian/Ubuntu systems that have been running SysV until now.

@tonyhutter
Copy link
Contributor Author

@loli10K do they break master as well?

@loli10K
Copy link
Contributor

loli10K commented Mar 9, 2018

Yes, but users running master should have different expectations about stability, some changes (e.g. removing a kernel module tunable) are "ok" in master.

Systems where this could be an issue:

  • Local admin has a custom configuration in /etc/rcX.d which is required by some other system using ZFS.
  • Monitoring systems using /etc/init.d/zfs-X scripts to check service availability (e.g. /etc/init.d/zfs-zed status)

What could be the repercussions of removing SysV scripts and installing Systemd unit files on such systems?

It's also true this issue could be easily avoided by reading the changelog/release notes.

@tonyhutter
Copy link
Contributor Author

@loli10K ok, I'm not sure of the repercussions of removing SysV either. I'll remove them from the patchset in my next push.

@loli10K
Copy link
Contributor

loli10K commented Mar 9, 2018

@tonyhutter thanks. To be fair, those changes would be very convenient in the latest release, i need them for my own boxes, but i'm worried about more "legacy" systems.

@tonyhutter
Copy link
Contributor Author

@loli10K Just so I'm 100% clear, you want these removed from the patchset right?: fbd4254 ee410ee

@loli10K
Copy link
Contributor

loli10K commented Mar 9, 2018

@tonyhutter yes, thanks, sorry for not being clear.

@tonyhutter tonyhutter force-pushed the zfs-0.7.7-hutter-squashed branch 2 times, most recently from 7852832 to 6e7b286 Compare March 13, 2018 00:56
This is a squashed patchset for zfs-0.7.7.  The individual commits are
in the tonyhutter:zfs-0.7.7-hutter branch.  I squashed the commits so
that buildbot wouldn't have to run against each one, and because
github/builbot seem to have a maximum limit of 30 commits they can
test from a PR.

- Fix MMP write frequency for large pools openzfs#7205 openzfs#7289
- Handle zio_resume and mmp => off openzfs#7286
- Fix zfs-kmod builds when using rpm >= 4.14 openzfs#7284
- zdb and inuse tests don't pass with real disks openzfs#6939 openzfs#7261
- Take user namespaces into account in policy checks openzfs#6800 openzfs#7270
- Detect long config lock acquisition in mmp openzfs#7212
- Linux 4.16 compat: get_disk_and_module() openzfs#7264
- Change checksum & IO delay ratelimit values openzfs#7252
- Increment zil_itx_needcopy_bytes properly openzfs#6988 openzfs#7176
- Fix some typos openzfs#7237
- Fix zpool(8) list example to match actual format openzfs#7244
- Add SMART self-test results to zpool status -c openzfs#7178
- Add scrub after resilver zed script openzfs#4662 openzfs#7086
- Fix free memory calculation on v3.14+ openzfs#7170
- Report duration and error in mmp_history entries openzfs#7190
- Do not initiate MMP writes while pool is suspended openzfs#7182
- Linux 4.16 compat: use correct *_dec_and_test()
- Allow modprobe to fail when called within systemd openzfs#7174
- Add SMART attributes for SSD and NVMe openzfs#7183 openzfs#7193
- Correct count_uberblocks in mmp.kshlib openzfs#7191
- Fix config issues: frame size and headers openzfs#7169
- Clarify zinject(8) explanation of -e openzfs#7172
- OpenZFS 8857 - zio_remove_child() panic due to already destroyed
  parent zio openzfs#7168
- 'zfs receive' fails with "dataset is busy" openzfs#7129 openzfs#7154
- contrib/initramfs: add missing conf.d/zfs openzfs#7158
- mmp should use a fixed tag for spa_config locks openzfs#6530 openzfs#7155
- Handle zap_add() failures in mixed case mode openzfs#7011 openzfs#7054
- Fix zdb -ed on objset for exported pool openzfs#7099 openzfs#6464
- Fix zdb -E segfault openzfs#7099
- Fix zdb -R decompression openzfs#7099 openzfs#4984
- Fix racy assignment of zcb.zcb_haderrors openzfs#7099
- Fix zle_decompress out of bound access openzfs#7099
- Fix zdb -c traverse stop on damaged objset root openzfs#7099
- Linux 4.11 compat: avoid refcount_t name conflict openzfs#7148
- Linux 4.16 compat: inode_set_iversion() openzfs#7148
- OpenZFS 8966 - Source file zfs_acl.c, function zfs_aclset_common
  contains a use after end of the lifetime of a local variable openzfs#7141
- Remove deprecated zfs_arc_p_aggressive_disable openzfs#7135
- Fix default libdir for Debian/Ubuntu openzfs#7083 openzfs#7101
- Bug fix in qat_compress.c for vmalloc addr check openzfs#7125
- Fix systemd_ RPM macros usage on Debian-based distributions openzfs#7074
  openzfs#7100
- Emit an error message before MMP suspends pool openzfs#7048
- ZTS: Fix create-o_ashift test case openzfs#6924 openzfs#6977
- Fix --with-systemd on Debian-based distributions (openzfs#6963) openzfs#6591 openzfs#6963
- Remove vn_rename and vn_remove dependency openzfs/spl#648 openzfs#6753
- Fix "--enable-code-coverage" debug build openzfs#6674
- Update codecov.yml openzfs#6669
- Add support for "--enable-code-coverage" option openzfs#6670
- Make "-fno-inline" compile option more accessible openzfs#6605
- Add configure option to enable gcov analysis openzfs#6642
- Implement --enable-debuginfo to force debuginfo openzfs#2734
- Make --enable-debug fail when given bogus args openzfs#2734

Signed-off-by: Tony Hutter <hutter2@llnl.gov>
Requires-spl: refs/pull/690/head
@tonyhutter tonyhutter force-pushed the zfs-0.7.7-hutter-squashed branch from 6e7b286 to fe5d27a Compare March 13, 2018 23:43
@codecov
Copy link

codecov bot commented Mar 14, 2018

Codecov Report

❗ No coverage uploaded for pull request base (zfs-0.7-release@e3b28e1). Click here to learn what that means.
The diff coverage is 75.34%.

@@                Coverage Diff                 @@
##             zfs-0.7-release    #7278   +/-   ##
==================================================
  Coverage                   ?   72.47%           
==================================================
  Files                      ?      289           
  Lines                      ?    89447           
  Branches                   ?        0           
==================================================
  Hits                       ?    64826           
  Misses                     ?    24621           
  Partials                   ?        0

@tonyhutter
Copy link
Contributor Author

@tonyhutter tonyhutter closed this Mar 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants