Message ID | 167320037778.1795566.14815059333113369420.stg-ugh@magnolia (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] xfs: bug fixes for 6.2 | expand |
On Sun, Jan 8, 2023 at 12:00 PM Darrick J. Wong <djwong@kernel.org> wrote: > > Please pull this branch with a pile of various bug fixes. This came in just as I was writing the rc3 announcement email, since I needed to get that done before I lose wifi again during travels today. Oh well, no biggie. > Speaking of problems: I'm in the process of updating my gpg key so that > I can do ed25519 signatures, but I still suck at using gpg(1) so wish me > luck. Heh. Not that I'm sure why rsa4096 wouldn't be good enough, but maybe you know something I don't... > The -fixes-2 tag should be signed by the same old rsa4096 key > that I've been using. I /think/ the -fixes-1 tag got signed with the > new subkey, but (afaict) the new subkey hasn't yet landed in > pgpkeys.git, so I went back to the old key so we can get the bugfixes > landed without blocking on maintainer stupidity. Or at least more > stupidity than usual. It's not like the keys have to be in pgpkeys.git.. You can always just sign the new key with the old key (which presumably y ou want to do anyway), and send me new key in email - or just use the key servers if they happen to work. But the old key obviously worked just fine. Thanks, Linus
The pull request you sent on Sun, 8 Jan 2023 10:00:43 -0800:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.2-fixes-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1fe4fd6f5cad346e598593af36caeadc4f5d4fa9
Thank you!
Hi Linus, Please pull this branch with a pile of various bug fixes. As usual, I did a test-merge with the main upstream branch as of a few minutes ago, and didn't see any conflicts. Please let me know if you encounter any problems. Speaking of problems: I'm in the process of updating my gpg key so that I can do ed25519 signatures, but I still suck at using gpg(1) so wish me luck. The -fixes-2 tag should be signed by the same old rsa4096 key that I've been using. I /think/ the -fixes-1 tag got signed with the new subkey, but (afaict) the new subkey hasn't yet landed in pgpkeys.git, so I went back to the old key so we can get the bugfixes landed without blocking on maintainer stupidity. Or at least more stupidity than usual. --D The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2: Linux 6.2-rc1 (2022-12-25 13:41:39 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.2-fixes-2 for you to fetch changes up to 601a27ea09a317d0fe2895df7d875381fb393041: xfs: fix extent busy updating (2023-01-05 07:34:21 -0800) ---------------------------------------------------------------- Fixes for 6.2-rc1: - Remove some incorrect assertions. - Fix compiler warnings about variables that could be static. - Fix an off by one error when computing the maximum btree height that can cause repair failures. - Fix the bulkstat-single ioctl not returning the root inode when asked to do that. - Convey NOFS state to inodegc workers to avoid recursion in reclaim. - Fix unnecessary variable initializations. - Fix a bug that could result in corruption of the busy extent tree. Signed-off-by: Darrick J. Wong <djwong@kernel.org> ---------------------------------------------------------------- Darrick J. Wong (3): xfs: don't assert if cmap covers imap after cycling lock xfs: make xfs_iomap_page_ops static xfs: fix off-by-one error in xfs_btree_space_to_height Hironori Shiina (1): xfs: get root inode correctly at bulkstat Li zeming (1): xfs: xfs_qm: remove unnecessary ‘0’ values from error Wengang Wang (1): xfs: fix extent busy updating Wu Guanghao (1): xfs: Fix deadlock on xfs_inodegc_worker fs/xfs/libxfs/xfs_btree.c | 7 ++++++- fs/xfs/xfs_extent_busy.c | 1 + fs/xfs/xfs_icache.c | 10 ++++++++++ fs/xfs/xfs_ioctl.c | 4 ++-- fs/xfs/xfs_iomap.c | 2 +- fs/xfs/xfs_qm.c | 2 +- fs/xfs/xfs_reflink.c | 2 -- 7 files changed, 21 insertions(+), 7 deletions(-)