[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 72/78] 9p: Lock directory streams with a CoMutex
From: |
Christian Schoenebeck |
Subject: |
Re: [PATCH 72/78] 9p: Lock directory streams with a CoMutex |
Date: |
Thu, 18 Jun 2020 15:47:50 +0200 |
On Mittwoch, 17. Juni 2020 00:46:26 CEST Michael Roth wrote:
> > > Indeed, for that particular stable branch I would see the following 9p
> > > fixes as additional candidates (chronologically top down):
> > >
> > > 841b8d099c [trivial] 9pfs: local: Fix possible memory leak in
> > > local_link()
> > > 846cf408a4 [maybe] 9p: local: always return -1 on error in
> > > local_unlinkat_common 9580d60e66 [maybe] virtio-9p-device: fix memleak
> > > in virtio_9p_device_unrealize 659f195328 [trivial] 9p/proxy: Fix
> > > export_flags
> > > a5804fcf7b [maybe] 9pfs: local: ignore O_NOATIME if we don't have
> > > permissions 03556ea920 [trivial] 9pfs: include linux/limits.h for
> > > XATTR_SIZE_MAX a4c4d46272 [recommended] xen/9pfs: yield when there
> > > isn't enough room on the ring
> > >
> > > What do you think Greg?
> >
> > AFAIK, only regressions and fixes to severe bugs (QEMU crashes, hangs,
> > CVEs) go to stable QEMU releases. It doesn't seem to be the case for any
> > of the commits listed above but I had only a quick look.
>
> That's the main focus, but if memory leaks and other minor fixes get tagged
> for stable I'll generally pull those in as well if the backport is fairly
> straightforward. As that was the case with the patches above I went
> ahead and pull those in.
>
> > > What's the recommended way for me to keep track of imminent stable
> > > picks/
> > > freezes in future?
> >
> > Hmm good question. I'm usually notified when Michael posts the patch
> > round-up and a 9p patch is already in the list, like for the present
> > patch. Other than that I watch qemu-stable from time to time or the
> > planning pages in the wiki.
> >
> > Michael, anything better to suggest to Christian ?
>
> I think that about covers it. You can also subscribe to the planning
> pages, e.g. https://wiki.qemu.org/Planning/5.0 (by clicking the
> star/"add to watchlist" icon), then you'll get notifications when
> additional release/freeze dates are added. Generally it will be updated
> shortly before the patch round-up gets posted to qemu-stable.
Good idea! Will do that.
Thanks Michael!
Best regards,
Christian Schoenebeck
- [PATCH 68/78] target/ppc: Fix mtmsr(d) L=1 variant that loses interrupts, (continued)
- [PATCH 68/78] target/ppc: Fix mtmsr(d) L=1 variant that loses interrupts, Michael Roth, 2020/06/16
- [PATCH 69/78] hostmem: don't use mbind() if host-nodes is empty, Michael Roth, 2020/06/16
- [PATCH 70/78] target/arm: Clear tail in gvec_fmul_idx_*, gvec_fmla_idx_*, Michael Roth, 2020/06/16
- [PATCH 06/78] block: Activate recursively even for already active nodes, Michael Roth, 2020/06/16
- [PATCH 71/78] qemu-nbd: Close inherited stderr, Michael Roth, 2020/06/16
- [PATCH 72/78] 9p: Lock directory streams with a CoMutex, Michael Roth, 2020/06/16
[PATCH 73/78] net: Do not include a newline in the id of -nic devices, Michael Roth, 2020/06/16
[PATCH 75/78] virtio-balloon: fix free page hinting without an iothread, Michael Roth, 2020/06/16
[PATCH 76/78] virtio-balloon: fix free page hinting check on unrealize, Michael Roth, 2020/06/16
[PATCH 74/78] nbd/server: Avoid long error message assertions CVE-2020-10761, Michael Roth, 2020/06/16
[PATCH 77/78] virtio-balloon: unref the iothread when unrealizing, Michael Roth, 2020/06/16
[PATCH 78/78] block: Call attention to truncation of long NBD exports, Michael Roth, 2020/06/16
[PATCH 07/78] virtio-blk: fix out-of-bounds access to bitmap in notify_guest_bh, Michael Roth, 2020/06/16
[PATCH 08/78] numa: remove not needed check, Michael Roth, 2020/06/16
Re: [PATCH 00/78] Patch Round-up for stable 4.2.1, freeze on 2020-06-22, Cole Robinson, 2020/06/17
Re: [PATCH 00/78] Patch Round-up for stable 4.2.1, freeze on 2020-06-22, Liam Merwick, 2020/06/17