Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Tue, Jun 07, 2016 at 05:52:52PM -0700, Guenter Roeck wrote: > Here we are; > > Build results: > total: 123 pass: 123 fail: 0 > Qemu test results: > total: 75 pass: 75 fail: 0 > > Details are available at http://kerneltests.org/builders. Excellent, thank you Guenter! Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Tue, Jun 07, 2016 at 05:52:52PM -0700, Guenter Roeck wrote: > Here we are; > > Build results: > total: 123 pass: 123 fail: 0 > Qemu test results: > total: 75 pass: 75 fail: 0 > > Details are available at http://kerneltests.org/builders. Excellent, thank you Guenter! Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On 06/07/2016 10:49 AM, Willy Tarreau wrote: Hi Guenter, On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote: Jiri provides a branch for 3.12, exactly as you suggested. In his case it is named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. Other testers such as kernelci.org pick it up from there (or from my repository after I pull it in). In my repository, all branches are named linux-.y.queue; for example, the 3.10 branch in my repository is named linux-3.10.y.queue. Those branches are also force-pushed when updated. OK then that's perfect, I'll do the same ASAP, probably today as time permits. Now done. Please find it here : git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git linux-3.10.y-queue It's a fork of Greg's linux-stable. I cleaned it up from irrelevant tags and branches. If you have any issue, please let me know. Here we are; Build results: total: 123 pass: 123 fail: 0 Qemu test results: total: 75 pass: 75 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On 06/07/2016 10:49 AM, Willy Tarreau wrote: Hi Guenter, On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote: Jiri provides a branch for 3.12, exactly as you suggested. In his case it is named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. Other testers such as kernelci.org pick it up from there (or from my repository after I pull it in). In my repository, all branches are named linux-.y.queue; for example, the 3.10 branch in my repository is named linux-3.10.y.queue. Those branches are also force-pushed when updated. OK then that's perfect, I'll do the same ASAP, probably today as time permits. Now done. Please find it here : git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git linux-3.10.y-queue It's a fork of Greg's linux-stable. I cleaned it up from irrelevant tags and branches. If you have any issue, please let me know. Here we are; Build results: total: 123 pass: 123 fail: 0 Qemu test results: total: 75 pass: 75 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Tue, Jun 07, 2016 at 07:49:53PM +0200, Willy Tarreau wrote: > > Now done. Please find it here : > > git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git > linux-3.10.y-queue > > It's a fork of Greg's linux-stable. I cleaned it up from irrelevant > tags and branches. If you have any issue, please let me know. > Excellent - picked up and building. I'll let you know once I have results; should be in a couple of hours. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Tue, Jun 07, 2016 at 07:49:53PM +0200, Willy Tarreau wrote: > > Now done. Please find it here : > > git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git > linux-3.10.y-queue > > It's a fork of Greg's linux-stable. I cleaned it up from irrelevant > tags and branches. If you have any issue, please let me know. > Excellent - picked up and building. I'll let you know once I have results; should be in a couple of hours. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
Hi Guenter, On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote: > > Jiri provides a branch for 3.12, exactly as you suggested. In his case it is > > named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and > > linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. > > Other testers such as kernelci.org pick it up from there (or from my > > repository > > after I pull it in). In my repository, all branches are named > > linux-.y.queue; > > for example, the 3.10 branch in my repository is named linux-3.10.y.queue. > > Those branches are also force-pushed when updated. > > OK then that's perfect, I'll do the same ASAP, probably today as time permits. Now done. Please find it here : git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git linux-3.10.y-queue It's a fork of Greg's linux-stable. I cleaned it up from irrelevant tags and branches. If you have any issue, please let me know. Thanks, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
Hi Guenter, On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote: > > Jiri provides a branch for 3.12, exactly as you suggested. In his case it is > > named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and > > linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. > > Other testers such as kernelci.org pick it up from there (or from my > > repository > > after I pull it in). In my repository, all branches are named > > linux-.y.queue; > > for example, the 3.10 branch in my repository is named linux-3.10.y.queue. > > Those branches are also force-pushed when updated. > > OK then that's perfect, I'll do the same ASAP, probably today as time permits. Now done. Please find it here : git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git linux-3.10.y-queue It's a fork of Greg's linux-stable. I cleaned it up from irrelevant tags and branches. If you have any issue, please let me know. Thanks, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Mon, Jun 06, 2016 at 10:59:27PM -0700, Guenter Roeck wrote: > On 06/06/2016 10:17 PM, Willy Tarreau wrote: > > On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: > > > > > Do you have a repository, either with the patch > > > > > series or with the to-be-tested branch, where the builder could > > > > > pick it up ? > > > > > > > > I don't but I can set something up for you. Would you be OK with a > > > > branch in my account (eg: "3.10-for-guenter") which I "git push -f" > > > > from my local branch ? That way you always pull from the same branch > > > > and we don't care if patches are removed during the process. Just let > > > > me know. Otherwise let me know if a different form is desired. > > > > > > > > > > Yes, that would be excellent. I would suggest to name it something like > > > stable-3.10-queue, though, to be a bit more generic. After all, other > > > testers will want to pick it up as well. > > > > Well, for me it would not be a "queue" in the sense of how Greg maintains > > it but more a release candidate derived from the last 3.10 tag. Basically > > if nothing changes between the review and the release, it will just get > > an extra commit which is the release tag. If I produce it just for your > > use case and you're fine with a force-pushed branch, I'd rather avoid to > > confuse other people who probably have no business using it. > > > > Jiri provides a branch for 3.12, exactly as you suggested. In his case it is > named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and > linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. > Other testers such as kernelci.org pick it up from there (or from my > repository > after I pull it in). In my repository, all branches are named > linux-.y.queue; > for example, the 3.10 branch in my repository is named linux-3.10.y.queue. > Those branches are also force-pushed when updated. OK then that's perfect, I'll do the same ASAP, probably today as time permits. Cheers, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Mon, Jun 06, 2016 at 10:59:27PM -0700, Guenter Roeck wrote: > On 06/06/2016 10:17 PM, Willy Tarreau wrote: > > On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: > > > > > Do you have a repository, either with the patch > > > > > series or with the to-be-tested branch, where the builder could > > > > > pick it up ? > > > > > > > > I don't but I can set something up for you. Would you be OK with a > > > > branch in my account (eg: "3.10-for-guenter") which I "git push -f" > > > > from my local branch ? That way you always pull from the same branch > > > > and we don't care if patches are removed during the process. Just let > > > > me know. Otherwise let me know if a different form is desired. > > > > > > > > > > Yes, that would be excellent. I would suggest to name it something like > > > stable-3.10-queue, though, to be a bit more generic. After all, other > > > testers will want to pick it up as well. > > > > Well, for me it would not be a "queue" in the sense of how Greg maintains > > it but more a release candidate derived from the last 3.10 tag. Basically > > if nothing changes between the review and the release, it will just get > > an extra commit which is the release tag. If I produce it just for your > > use case and you're fine with a force-pushed branch, I'd rather avoid to > > confuse other people who probably have no business using it. > > > > Jiri provides a branch for 3.12, exactly as you suggested. In his case it is > named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and > linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. > Other testers such as kernelci.org pick it up from there (or from my > repository > after I pull it in). In my repository, all branches are named > linux-.y.queue; > for example, the 3.10 branch in my repository is named linux-3.10.y.queue. > Those branches are also force-pushed when updated. OK then that's perfect, I'll do the same ASAP, probably today as time permits. Cheers, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On 06/06/2016 10:17 PM, Willy Tarreau wrote: On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: Do you have a repository, either with the patch series or with the to-be-tested branch, where the builder could pick it up ? I don't but I can set something up for you. Would you be OK with a branch in my account (eg: "3.10-for-guenter") which I "git push -f" from my local branch ? That way you always pull from the same branch and we don't care if patches are removed during the process. Just let me know. Otherwise let me know if a different form is desired. Yes, that would be excellent. I would suggest to name it something like stable-3.10-queue, though, to be a bit more generic. After all, other testers will want to pick it up as well. Well, for me it would not be a "queue" in the sense of how Greg maintains it but more a release candidate derived from the last 3.10 tag. Basically if nothing changes between the review and the release, it will just get an extra commit which is the release tag. If I produce it just for your use case and you're fine with a force-pushed branch, I'd rather avoid to confuse other people who probably have no business using it. Jiri provides a branch for 3.12, exactly as you suggested. In his case it is named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. Other testers such as kernelci.org pick it up from there (or from my repository after I pull it in). In my repository, all branches are named linux-.y.queue; for example, the 3.10 branch in my repository is named linux-3.10.y.queue. Those branches are also force-pushed when updated. Having said that, as long as you make it available, please feel free to name the branch as you like. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On 06/06/2016 10:17 PM, Willy Tarreau wrote: On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: Do you have a repository, either with the patch series or with the to-be-tested branch, where the builder could pick it up ? I don't but I can set something up for you. Would you be OK with a branch in my account (eg: "3.10-for-guenter") which I "git push -f" from my local branch ? That way you always pull from the same branch and we don't care if patches are removed during the process. Just let me know. Otherwise let me know if a different form is desired. Yes, that would be excellent. I would suggest to name it something like stable-3.10-queue, though, to be a bit more generic. After all, other testers will want to pick it up as well. Well, for me it would not be a "queue" in the sense of how Greg maintains it but more a release candidate derived from the last 3.10 tag. Basically if nothing changes between the review and the release, it will just get an extra commit which is the release tag. If I produce it just for your use case and you're fine with a force-pushed branch, I'd rather avoid to confuse other people who probably have no business using it. Jiri provides a branch for 3.12, exactly as you suggested. In his case it is named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. Other testers such as kernelci.org pick it up from there (or from my repository after I pull it in). In my repository, all branches are named linux-.y.queue; for example, the 3.10 branch in my repository is named linux-3.10.y.queue. Those branches are also force-pushed when updated. Having said that, as long as you make it available, please feel free to name the branch as you like. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: > > > Do you have a repository, either with the patch > > > series or with the to-be-tested branch, where the builder could > > > pick it up ? > > > > I don't but I can set something up for you. Would you be OK with a > > branch in my account (eg: "3.10-for-guenter") which I "git push -f" > > from my local branch ? That way you always pull from the same branch > > and we don't care if patches are removed during the process. Just let > > me know. Otherwise let me know if a different form is desired. > > > > Yes, that would be excellent. I would suggest to name it something like > stable-3.10-queue, though, to be a bit more generic. After all, other > testers will want to pick it up as well. Well, for me it would not be a "queue" in the sense of how Greg maintains it but more a release candidate derived from the last 3.10 tag. Basically if nothing changes between the review and the release, it will just get an extra commit which is the release tag. If I produce it just for your use case and you're fine with a force-pushed branch, I'd rather avoid to confuse other people who probably have no business using it. Thanks, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: > > > Do you have a repository, either with the patch > > > series or with the to-be-tested branch, where the builder could > > > pick it up ? > > > > I don't but I can set something up for you. Would you be OK with a > > branch in my account (eg: "3.10-for-guenter") which I "git push -f" > > from my local branch ? That way you always pull from the same branch > > and we don't care if patches are removed during the process. Just let > > me know. Otherwise let me know if a different form is desired. > > > > Yes, that would be excellent. I would suggest to name it something like > stable-3.10-queue, though, to be a bit more generic. After all, other > testers will want to pick it up as well. Well, for me it would not be a "queue" in the sense of how Greg maintains it but more a release candidate derived from the last 3.10 tag. Basically if nothing changes between the review and the release, it will just get an extra commit which is the release tag. If I produce it just for your use case and you're fine with a force-pushed branch, I'd rather avoid to confuse other people who probably have no business using it. Thanks, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
Hi Willy, On 06/06/2016 09:09 PM, Willy Tarreau wrote: Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: The whole patch series can be found in one patch at : https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz Hi Willy, my auto-builder can not pick up a stable release candidate from a tarball like this. I guess you mean from a patch, since it's a patch and not a tarball :-) Whatever it is :-) Do you have a repository, either with the patch series or with the to-be-tested branch, where the builder could pick it up ? I don't but I can set something up for you. Would you be OK with a branch in my account (eg: "3.10-for-guenter") which I "git push -f" from my local branch ? That way you always pull from the same branch and we don't care if patches are removed during the process. Just let me know. Otherwise let me know if a different form is desired. Yes, that would be excellent. I would suggest to name it something like stable-3.10-queue, though, to be a bit more generic. After all, other testers will want to pick it up as well. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
Hi Willy, On 06/06/2016 09:09 PM, Willy Tarreau wrote: Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: The whole patch series can be found in one patch at : https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz Hi Willy, my auto-builder can not pick up a stable release candidate from a tarball like this. I guess you mean from a patch, since it's a patch and not a tarball :-) Whatever it is :-) Do you have a repository, either with the patch series or with the to-be-tested branch, where the builder could pick it up ? I don't but I can set something up for you. Would you be OK with a branch in my account (eg: "3.10-for-guenter") which I "git push -f" from my local branch ? That way you always pull from the same branch and we don't care if patches are removed during the process. Just let me know. Otherwise let me know if a different form is desired. Yes, that would be excellent. I would suggest to name it something like stable-3.10-queue, though, to be a bit more generic. After all, other testers will want to pick it up as well. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: > On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: > > The whole patch series can be found in one patch at : > > > > https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz > > > > Hi Willy, > > my auto-builder can not pick up a stable release candidate from a > tarball like this. I guess you mean from a patch, since it's a patch and not a tarball :-) > Do you have a repository, either with the patch > series or with the to-be-tested branch, where the builder could > pick it up ? I don't but I can set something up for you. Would you be OK with a branch in my account (eg: "3.10-for-guenter") which I "git push -f" from my local branch ? That way you always pull from the same branch and we don't care if patches are removed during the process. Just let me know. Otherwise let me know if a different form is desired. > Also, it would be helpful if you can copy me (li...@roeck-us.net) > on release annoucements like this. OK, noted. Thanks, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: > On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: > > The whole patch series can be found in one patch at : > > > > https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz > > > > Hi Willy, > > my auto-builder can not pick up a stable release candidate from a > tarball like this. I guess you mean from a patch, since it's a patch and not a tarball :-) > Do you have a repository, either with the patch > series or with the to-be-tested branch, where the builder could > pick it up ? I don't but I can set something up for you. Would you be OK with a branch in my account (eg: "3.10-for-guenter") which I "git push -f" from my local branch ? That way you always pull from the same branch and we don't care if patches are removed during the process. Just let me know. Otherwise let me know if a different form is desired. > Also, it would be helpful if you can copy me (li...@roeck-us.net) > on release annoucements like this. OK, noted. Thanks, Willy
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: > This is the start of the stable review cycle for the 3.10.102 release. > All patches will be posted as a response to this one. If anyone has any > issue with these being applied, please let me know. If anyone thinks some > important patches are missing and should be added prior to the release, > please report them quickly with their respective mainline commit IDs. > > Responses should be made by Sat Jun 11 11:48:43 CEST 2016. > Anything received after that time might be too late. If someone > wants a bit more time for a deeper review, please let me know. > > The whole patch series can be found in one patch at : > > https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz > Hi Willy, my auto-builder can not pick up a stable release candidate from a tarball like this. Do you have a repository, either with the patch series or with the to-be-tested branch, where the builder could pick it up ? Also, it would be helpful if you can copy me (li...@roeck-us.net) on release annoucements like this. Thanks, Guenter
Re: [PATCH 3.10 000/143] 3.10.102-stable review
On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: > This is the start of the stable review cycle for the 3.10.102 release. > All patches will be posted as a response to this one. If anyone has any > issue with these being applied, please let me know. If anyone thinks some > important patches are missing and should be added prior to the release, > please report them quickly with their respective mainline commit IDs. > > Responses should be made by Sat Jun 11 11:48:43 CEST 2016. > Anything received after that time might be too late. If someone > wants a bit more time for a deeper review, please let me know. > > The whole patch series can be found in one patch at : > > https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz > Hi Willy, my auto-builder can not pick up a stable release candidate from a tarball like this. Do you have a repository, either with the patch series or with the to-be-tested branch, where the builder could pick it up ? Also, it would be helpful if you can copy me (li...@roeck-us.net) on release annoucements like this. Thanks, Guenter
[PATCH 3.10 000/143] 3.10.102-stable review
This is the start of the stable review cycle for the 3.10.102 release. All patches will be posted as a response to this one. If anyone has any issue with these being applied, please let me know. If anyone thinks some important patches are missing and should be added prior to the release, please report them quickly with their respective mainline commit IDs. Responses should be made by Sat Jun 11 11:48:43 CEST 2016. Anything received after that time might be too late. If someone wants a bit more time for a deeper review, please let me know. The whole patch series can be found in one patch at : https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz The shortlog and diffstat are appended below. Thanks, Willy === Aaro Koskinen (1): mtd: onenand: fix deadlock in onenand_block_markbad Adrian Hunter (1): mmc: mmc: Fix partition switch timeout for some eMMCs Al Viro (1): get_rock_ridge_filename(): handle malformed NM entries Alan Stern (1): HID: usbhid: fix inconsistent reset/resume/reset-resume behavior Alexey Khoroshilov (2): [media] usbvision-video: fix memory leak of alt_max_pkt_size usbvision: fix leak of usb_dev on failure paths in usbvision_probe() Andi Kleen (2): perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere asmlinkage, pnp: Make variables used from assembler code visible Andrey Gelman (1): Input: ads7846 - correct the value got from SPI Andy Lutomirski (1): x86/iopl: Fix iopl capability check on Xen PV Anton Blanchard (1): powerpc: scan_features() updates incorrect bits for REAL_LE Arnaldo Carvalho de Melo (1): net: Fix use after free in the recvmmsg exit path Arnd Bergmann (5): farsync: fix off-by-one bug in fst_add_one ath9k: fix buffer overrun for ar9287 ASoC: s3c24xx: use const snd_soc_component_driver pointer paride: make 'verbose' parameter an 'int' again lpfc: fix misleading indentation Aurelien Jacquiot (1): rapidio/rionet: fix deadlock on SMP Behan Webster (1): x86: LLVMLinux: Fix "incomplete type const struct x86cpu_device_id" Ben Hutchings (3): pipe: Fix buffer offset after partially failed read misc/bmp085: Enable building as a module atl2: Disable unimplemented scatter/gather feature Bill Sommerfeld (1): udp6: fix UDP/IPv6 encap resubmit path Bjorn Helgaas (1): PCI: Disable IO/MEM decoding for devices with non-compliant BARs Bj�rn Mork (3): USB: option: add "D-Link DWM-221 B1" device id cdc_ncm: toggle altsetting to force reset before setup qmi_wwan: add "D-Link DWM-221 B1" device id Borislav Petkov (1): perf stat: Document --detailed option Chanwoo Choi (1): serial: samsung: Reorder the sequence of clock control when call s3c24xx_serial_set_termios() Chris Friesen (1): route: do not cache fib route info on local routes with oif Dan Carpenter (1): EDAC, amd64_edac: Shift wrapping issue in f1x_get_norm_dct_addr() Dan Streetman (1): nbd: ratelimit error msgs after socket close David S. Miller (1): decnet: Do not build routes to devices without decnet private data. Diego Viola (1): net: jme: fix suspend/resume on JMC260 Dmitry Ivanov (1): nl80211: check netlink protocol in socket release notification Douglas Gilbert (1): sg: fix dxferp in from_to case Eric Wheeler (1): bcache: fix cache_set_flush() NULL pointer dereference on OOM Eryu Guan (1): ext4: fix NULL pointer dereference in ext4_mark_inode_dirty() Florian Westphal (1): ipv6: re-enable fragment header matching in ipv6_find_hdr Gabriel Krisman Bertazi (1): ipr: Fix regression when loading firmware Geert Uytterhoeven (1): rtc: vr41xx: Wire up alarm_irq_enable Guenter Roeck (1): hwmon: (max) Return -ENODEV from max_read_channel if not instantiated Guillaume Nault (1): ppp: take reference on channels netns H. Peter Anvin (3): linux/const.h: Add _BITUL() and _BITULL() x86: Rename X86_CR4_RDWRGSFS to X86_CR4_FSGSBASE x86, processor-flags: Fix the datatypes and add bit number defines Haishuang Yan (2): ipv4: l2tp: fix a potential issue in l2tp_ip_recv ipv6: l2tp: fix a potential issue in l2tp_ip6_recv Hans de Goede (2): pwc: Add USB id for Philips Spc880nc webcam bttv: Width must be a multiple of 16 when capturing planar formats Helge Deller (2): parisc: Avoid function pointers for kernel exception routines parisc: Fix kernel crash with reversed copy_from_user() Herbert Xu (2): crypto: gcm - Fix rfc4543 decryption crash crypto: hash - Fix page length clamping in hash walk Ian Campbell (1): VSOCK: do not disconnect socket when peer has shutdown SEND only Ignat Korchagin (1): USB: usbip: fix potential out-of-bounds write Insu Yun (1): ipr: Fix out-of-bounds null overwrite Jasem Mutlaq (1): USB: serial: cp210x: add Straizona Focusers device ids Jes Sorensen (1): md/raid5: Compare apples to apples (or sectors to sectors) Jiri Slaby (2): Bluetooth: vhci: purge unhandled skbs tty: vt, return error
[PATCH 3.10 000/143] 3.10.102-stable review
This is the start of the stable review cycle for the 3.10.102 release. All patches will be posted as a response to this one. If anyone has any issue with these being applied, please let me know. If anyone thinks some important patches are missing and should be added prior to the release, please report them quickly with their respective mainline commit IDs. Responses should be made by Sat Jun 11 11:48:43 CEST 2016. Anything received after that time might be too late. If someone wants a bit more time for a deeper review, please let me know. The whole patch series can be found in one patch at : https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz The shortlog and diffstat are appended below. Thanks, Willy === Aaro Koskinen (1): mtd: onenand: fix deadlock in onenand_block_markbad Adrian Hunter (1): mmc: mmc: Fix partition switch timeout for some eMMCs Al Viro (1): get_rock_ridge_filename(): handle malformed NM entries Alan Stern (1): HID: usbhid: fix inconsistent reset/resume/reset-resume behavior Alexey Khoroshilov (2): [media] usbvision-video: fix memory leak of alt_max_pkt_size usbvision: fix leak of usb_dev on failure paths in usbvision_probe() Andi Kleen (2): perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere asmlinkage, pnp: Make variables used from assembler code visible Andrey Gelman (1): Input: ads7846 - correct the value got from SPI Andy Lutomirski (1): x86/iopl: Fix iopl capability check on Xen PV Anton Blanchard (1): powerpc: scan_features() updates incorrect bits for REAL_LE Arnaldo Carvalho de Melo (1): net: Fix use after free in the recvmmsg exit path Arnd Bergmann (5): farsync: fix off-by-one bug in fst_add_one ath9k: fix buffer overrun for ar9287 ASoC: s3c24xx: use const snd_soc_component_driver pointer paride: make 'verbose' parameter an 'int' again lpfc: fix misleading indentation Aurelien Jacquiot (1): rapidio/rionet: fix deadlock on SMP Behan Webster (1): x86: LLVMLinux: Fix "incomplete type const struct x86cpu_device_id" Ben Hutchings (3): pipe: Fix buffer offset after partially failed read misc/bmp085: Enable building as a module atl2: Disable unimplemented scatter/gather feature Bill Sommerfeld (1): udp6: fix UDP/IPv6 encap resubmit path Bjorn Helgaas (1): PCI: Disable IO/MEM decoding for devices with non-compliant BARs Bj�rn Mork (3): USB: option: add "D-Link DWM-221 B1" device id cdc_ncm: toggle altsetting to force reset before setup qmi_wwan: add "D-Link DWM-221 B1" device id Borislav Petkov (1): perf stat: Document --detailed option Chanwoo Choi (1): serial: samsung: Reorder the sequence of clock control when call s3c24xx_serial_set_termios() Chris Friesen (1): route: do not cache fib route info on local routes with oif Dan Carpenter (1): EDAC, amd64_edac: Shift wrapping issue in f1x_get_norm_dct_addr() Dan Streetman (1): nbd: ratelimit error msgs after socket close David S. Miller (1): decnet: Do not build routes to devices without decnet private data. Diego Viola (1): net: jme: fix suspend/resume on JMC260 Dmitry Ivanov (1): nl80211: check netlink protocol in socket release notification Douglas Gilbert (1): sg: fix dxferp in from_to case Eric Wheeler (1): bcache: fix cache_set_flush() NULL pointer dereference on OOM Eryu Guan (1): ext4: fix NULL pointer dereference in ext4_mark_inode_dirty() Florian Westphal (1): ipv6: re-enable fragment header matching in ipv6_find_hdr Gabriel Krisman Bertazi (1): ipr: Fix regression when loading firmware Geert Uytterhoeven (1): rtc: vr41xx: Wire up alarm_irq_enable Guenter Roeck (1): hwmon: (max) Return -ENODEV from max_read_channel if not instantiated Guillaume Nault (1): ppp: take reference on channels netns H. Peter Anvin (3): linux/const.h: Add _BITUL() and _BITULL() x86: Rename X86_CR4_RDWRGSFS to X86_CR4_FSGSBASE x86, processor-flags: Fix the datatypes and add bit number defines Haishuang Yan (2): ipv4: l2tp: fix a potential issue in l2tp_ip_recv ipv6: l2tp: fix a potential issue in l2tp_ip6_recv Hans de Goede (2): pwc: Add USB id for Philips Spc880nc webcam bttv: Width must be a multiple of 16 when capturing planar formats Helge Deller (2): parisc: Avoid function pointers for kernel exception routines parisc: Fix kernel crash with reversed copy_from_user() Herbert Xu (2): crypto: gcm - Fix rfc4543 decryption crash crypto: hash - Fix page length clamping in hash walk Ian Campbell (1): VSOCK: do not disconnect socket when peer has shutdown SEND only Ignat Korchagin (1): USB: usbip: fix potential out-of-bounds write Insu Yun (1): ipr: Fix out-of-bounds null overwrite Jasem Mutlaq (1): USB: serial: cp210x: add Straizona Focusers device ids Jes Sorensen (1): md/raid5: Compare apples to apples (or sectors to sectors) Jiri Slaby (2): Bluetooth: vhci: purge unhandled skbs tty: vt, return error
