| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <8738rjayff.wl%satoru.takeuchi@gmail.com> Date: Sat, 13 Jul 2013 13:14:44 +0900 From: Satoru Takeuchi <satoru.takeuchi@...il.com> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, stable@...r.kernel.org Subject: Re: [ 00/19] 3.10.1-stable review At Thu, 11 Jul 2013 15:01:17 -0700, Greg Kroah-Hartman wrote: > > <rant> > I'm sitting on top of over 170 more patches that have been marked for > the stable releases right now that are not included in this set of > releases. The fact that there are this many patches for stable stuff > that are waiting to be merged through the main -rc1 merge window cycle > is worrying to me. > > Why are subsystem maintainers holding on to fixes that are > _supposedly_ affecting all users? I mean, 21 powerpc core changes > that I don't see until a -rc1 merge? It's as if developers don't > expect people to use a .0 release and are relying on me to get the > fixes they have burried in their trees out to users. That's not that > nice. 6 "core" iscsi-target fixes? That's the sign of either a > broken subsystem maintainer, or a lack of understanding what the > normal -rc kernel releases are supposed to be for. > > So, I've picked through the patches and dug out only those that I've > "guessed" at being more important than others for the 3.10.1 release. > I'll get to the rest of these after 3.11-rc1 is out, and eventually > they will make it into the stable releases, but I am going to be much > more strict as to what is being added (carriage return changes for > debug messages, really ACPI developers?) > > </rant> > > This is the start of the stable review cycle for the 3.10.1 release. > There are 19 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat Jul 13 21:45:35 UTC 2013. > Anything received after that time might be too late. > This kernel can be built and boot without any problem. Building a kernel with this kernel also works fine. - Build Machine: debian jessy x86_64 CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4 memory: 8GB - Test machine: debian jessy x86_64(KVM guest on the Build Machine) vCPU: x2 memory: 2GB Thanks, Satoru > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.1-rc1.gz > and the diffstat can be found below. > > thanks, > > greg k-h > > ------------- > Pseudo-Shortlog of commits: > > Greg Kroah-Hartman <gregkh@...uxfoundation.org> > Linux 3.10.1-rc1 > > Michal Hocko <mhocko@...e.cz> > Revert "memcg: avoid dangling reference count in creation failure" > > Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com> > cpufreq: Fix cpufreq regression after suspend/resume > > Ben Hutchings <ben@...adent.org.uk> > SCSI: sd: Fix parsing of 'temporary ' cache mode prefix > > Gleb Natapov <gleb@...hat.com> > KVM: VMX: mark unusable segment as nonpresent > > J. Bruce Fields <bfields@...hat.com> > nfsd4: fix decoding of compounds across page boundaries > > Andy Adamson <andros@...app.com> > NFSv4.1 end back channel session draining > > Greg Kroah-Hartman <gregkh@...uxfoundation.org> > Revert "serial: 8250_pci: add support for another kind of NetMos Technology PCI 9835 Multi-I/O Controller" > > Peter Hurley <peter@...leysoftware.com> > tty: Reset itty for other pty > > Zhang Yi <wetpzy@...il.com> > futex: Take hugepages into account when generating futex_key > > Greg Kroah-Hartman <gregkh@...uxfoundation.org> > MAINTAINERS: add stable_kernel_rules.txt to stable maintainer information > > Kees Cook <keescook@...omium.org> > crypto: sanitize argument for format string > > Kees Cook <keescook@...omium.org> > block: do not pass disk names as format strings > > Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz> > hpfs: better test for errors > > Kees Cook <keescook@...omium.org> > charger-manager: Ensure event is not used as format string > > Rusty Russell <rusty@...tcorp.com.au> > module: do percpu allocation after uniqueness check. No, really! > > Jonathan Salwan <jonathan.salwan@...il.com> > drivers/cdrom/cdrom.c: use kzalloc() for failing hardware > > Josh Durgin <josh.durgin@...tank.com> > libceph: fix invalid unsigned->signed conversion for timespec encoding > > majianpeng <majianpeng@...il.com> > ceph: fix sleeping function called from invalid context. > > Tyler Hicks <tyhicks@...onical.com> > libceph: Fix NULL pointer dereference in auth client code > > > ------------- > > Diffstat: > > MAINTAINERS | 1 + > Makefile | 4 ++-- > arch/x86/kvm/vmx.c | 11 +++++++++-- > block/genhd.c | 2 +- > crypto/algapi.c | 3 ++- > drivers/block/nbd.c | 3 ++- > drivers/cdrom/cdrom.c | 2 +- > drivers/cpufreq/cpufreq_stats.c | 1 + > drivers/power/charger-manager.c | 2 +- > drivers/scsi/osd/osd_uld.c | 2 +- > drivers/scsi/sd.c | 2 +- > drivers/tty/serial/8250/8250_pci.c | 4 ---- > drivers/tty/tty_io.c | 2 ++ > fs/ceph/xattr.c | 9 +++++---- > fs/hpfs/map.c | 3 ++- > fs/hpfs/super.c | 8 +++++++- > fs/nfs/nfs4state.c | 23 +++++++++++------------ > fs/nfsd/nfs4xdr.c | 2 +- > include/linux/ceph/decode.h | 5 ----- > include/linux/hugetlb.h | 16 ++++++++++++++++ > kernel/futex.c | 3 ++- > kernel/module.c | 34 ++++++++++++++++++---------------- > mm/hugetlb.c | 17 +++++++++++++++++ > mm/memcontrol.c | 2 -- > net/ceph/auth_none.c | 6 ++++++ > 25 files changed, 109 insertions(+), 58 deletions(-) > > > -- > To unsubscribe from this list: send the line "unsubscribe stable" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists