Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=v6.12.80 2024-10-18T04:49:48+00:00 2024-10-18T04:49:48+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-10-14T01:53:26+00:00 urn:sha1:a0d11feefb1998204f095fa0400024403d233108 Using commit_do() to call alloc_sectors_start_trans() breaks when we're randomly injecting transaction restarts - the restart in the commit causes us to leak the lock that alloc_sectorS_start_trans() takes. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-10-18T04:49:48+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-10-15T03:58:45+00:00 urn:sha1:6bee2a04c5473d6d463c64e9a1f77c875b83401d bch2_bucket_io_time_reset() doesn't need to succeed, which is why it didn't previously retry on transaction restart - but we're now treating these as errors. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-10-18T04:49:47+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-10-15T06:13:22+00:00 urn:sha1:7ee4be9c621e4cd6a87d134a46d7c56debdf6664 this one is fairly harmless since the invalidate worker will just run again later if it needs to, but still worth fixing Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-10-13T21:55:33+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-10-12T19:49:23+00:00 urn:sha1:a319aeaebb6c7d8e68125943d454031b27d6b3ef We were checking that the alloc key was for a valid device, but not a valid bucket. This is the upgrade path from versions prior to bcachefs being mainlined. Reported-by: syzbot+a1b59c8e1a3f022fd301@syzkaller.appspotmail.com Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-10-05T00:25:32+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-10-01T23:08:37+00:00 urn:sha1:260af1562ec14353824da24fe7acc179a902558e The fragmentation_lru field hasn't been needed since we reworked the LRU btrees to use the btree write buffer; previously it was used to resolve collisions, but the revised LRU btree uses the backpointer (the bucket) as part of the key. It should have been deleted at the time of the LRU rework; since it wasn't, that left places for bugs to hide, in check/repair. This fixes LRU fsck on a filesystem image helpfully provided by a user who disappeared before I could get his name for the reported-by. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-09-21T15:39:49+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-09-06T23:12:53+00:00 urn:sha1:83ccd9b31d5356f9943b8fd0f996ec9fefcb25f1 Add a counter that's incremented whenever rw devices change; this will be used for erasure coding so that it can keep ec_stripe_head in sync and not deadlock on a new stripe when a device it wants goes away. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-09-21T15:39:49+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-09-01T22:35:52+00:00 urn:sha1:ad8d1f77fc425f42d1b297486eea36864ae82c41 We can now correctly force-remove a device that has stripes on it; this uses the new BCH_SB_MEMBER_INVALID sentinal value. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-09-21T15:39:48+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-09-01T21:56:27+00:00 urn:sha1:6b812f1dcebfee45d9ef6856404fa666797ac979 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-09-09T13:41:49+00:00 Chen Yufan chenyufan@vivo.com 2024-08-22T02:57:31+00:00 urn:sha1:848c3ff8826b68a587f84f1b00556ab8af651bef Use jiffies macros instead of using jiffies directly to handle wraparound. Signed-off-by: Chen Yufan <chenyufan@vivo.com> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 2024-09-09T13:41:46+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-09-04T19:48:59+00:00 urn:sha1:5a6e43af1e5341a11a719270cef9d846b0bbfaa5 ca->io_ref does not protect against the filesystem going way, c->write_ref does. Much like 0b50b7313ef2 bcachefs: Fix refcounting in discard path the other async paths need fixing. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>