Re: [PATCH 2/5] cifsd: add server-side procedures for SMB3

Am 23.03.2021 um 08:19 schrieb Dan Carpenter: On Tue, Mar 23, 2021 at 08:17:47AM +0900, Namjae Jeon wrote: + +static int +compare_oid(unsigned long *oid1, unsigned int oid1len, + unsigned long *oid2, unsigned int oid2len) { + unsigned int i; + + if (oid1len != oid2len) +

Re: [PATCH v21 10/10] fs/ntfs3: Add MAINTAINERS

Am 12.02.2021 um 17:24 schrieb Konstantin Komarov: This adds MAINTAINERS Signed-off-by: Konstantin Komarov just for your info with latest ntfs3 driver kern.err kernel: ntfs3: sda1: ntfs_evict_inode r=fe1 failed, -22.

Re: [RFC 0/7] Add support to process rx packets in thread

i agree. i just can say that i tested this patch recently due this discussion here. and it can be changed by sysfs. but it doesnt work for wifi drivers which are mainly using dummy netdev devices. for this i made a small patch to get them working using napi_set_threaded manually hardcoded in

Re: [RFC 0/7] Add support to process rx packets in thread

Am 25.07.2020 um 14:25 schrieb Hillf Danton: On Sat, 25 Jul 2020 12:38:00 +0200 Sebastian Gottschall wrote: you may consider this https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1142611.html <https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1142611.html>

Re: [RFC 0/7] Add support to process rx packets in thread

you may consider this https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1142611.html years ago someone already wanted to bring this feature upstream, but it was denied. i already tested this patch the last

Re: [RFC 7/7] ath10k: Handle rx thread suspend and resume

your patch seem to only affect the WCN3990 chipset. all other ath10k supported chipset are not supported here. so you see a chance to implement this more generic? Sebastian Am 21.07.2020 um 19:14 schrieb Rakesh Pillai: During the system suspend or resume, the rx thread also needs to be

Re: [PATCH 4.14 00/78] 4.14.186-rc1 review

this patch is broken. 4.14.186 has been already released. the patch shows just conflicts Am 29.06.2020 um 17:36 schrieb Sasha Levin: This is the start of the stable review cycle for the 4.14.186 release. There are 78 patches in this series, all will be posted as a response to this one. If

possible fix for broken cmac crypto support

19 um 16:36 schrieb Sebastian Gottschall: by the way. this big fat kernel warning exists in all operation modes unless anything else but aes-128 ccmp is used. since the chipset is capable of doing gcmp etc. as well it would be nice if this issue can be fixed. otherwise encryption support can be

Re: [PATCH] mt76: mt7615: add support for per-chain signal strength reporting

okay. curious is, that my variant works with sane results too. i will test your variant and check the results Sebastian Am 10.06.2019 um 06:22 schrieb Ryder Lee: On Mon, 2019-06-10 at 10:09 +0800, Ryder Lee wrote: On Sun, 2019-06-09 at 16:44 +0200, Sebastian Gottschall wrote: according to my

Re: [PATCH] mt76: mt7615: add support for per-chain signal strength reporting

according to my findings MT_RXV4_RCPI1 is part of rx descriptor 4 and not 3 so it must be rxdg4 = rxd[4] etc. however rxdg3 contains MT_RXV3_IB_RSSIRX which can be used for signal calculation. i already wrote a similar code for this driver which i sended to felix a long time ago. my variant

Re: [PATCH v3 1/2] mt76: mt7615: enable support for mesh

by the way. this big fat kernel warning exists in all operation modes unless anything else but aes-128 ccmp is used. since the chipset is capable of doing gcmp etc. as well it would be nice if this issue can be fixed. otherwise encryption support can be defined as "broken" for mt7615 Am

Re: [PATCH v3 1/2] mt76: mt7615: enable support for mesh

Am 06.06.2019 um 18:19 schrieb Lorenzo Bianconi: i tested your patch against a qca 9984 chipset using SAE and without encryption. both did not work. the devices are connecting, but no data connection is possible Hi Sebastian, I tested Ryder's patch using mt76x2 as mesh peer and it works fine

Re: [PATCH v3 1/2] mt76: mt7615: enable support for mesh

in addition you should take care about this problem which is raised up if SAE is used. since AES-CMAC required tid to be non zero WARNING: CPU: 2 PID: 15324 at /home/seg/DEV/mt7621/src/router/private/compat-wireless-2017-09-03/net/mac80211/key.c:1096 mt76_wcid_key_setup+0x58/0x9c [mt76]

Re: [PATCH v3 1/2] mt76: mt7615: enable support for mesh

i tested your patch against a qca 9984 chipset using SAE and without encryption. both did not work. the devices are connecting, but no data connection is possible Sebastian Am 03.06.2019 um 08:08 schrieb Ryder Lee: Enable NL80211_IFTYPE_MESH_POINT and update its path. Signed-off-by: Ryder

Re: [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export

Am 07.05.2019 um 12:31 schrieb David Laight: ... So I don't really see a problem with Andy's patch. If we want to annoy external non-GPL modules as much as possible, sure, that's for a separate discussion though (and I am sure many people would agree to that). Proposal to get rid of

Re: [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export

Am 04.05.2019 um 02:47 schrieb Ingo Molnar: * Jiri Kosina wrote: On Thu, 2 May 2019, Sebastian Andrzej Siewior wrote: Please don't start this. We have everything _GPL that is used for FPU related code and only a few functions are exported because KVM needs it. That's not completely true.

Re: [PATCH 4.19 01/24] bridge: do not add port to router list when receives query with source 0.0.0.0

Am 20.02.2019 um 15:46 schrieb Hangbin Liu: Could you please include more details about the setup that's broken ? Note that we were warned[1] of potential breakage from this change Sorry I missed Linus's reply after Ying Xu replied. I will read it and disscuss with Ying Xu. after it went in

Re: [PATCH 4.19 01/24] bridge: do not add port to router list when receives query with source 0.0.0.0

*reminder* Am 18.02.2019 um 11:18 schrieb Sebastian Gottschall: Am 17.02.2019 um 17:48 schrieb Greg Kroah-Hartman: On Sun, Feb 17, 2019 at 03:29:22PM +0100, Sebastian Gottschall wrote: according to user reports this patch will cause a serious regression. igmp snooping is not working anymore

Re: [PATCH 4.19 01/24] bridge: do not add port to router list when receives query with source 0.0.0.0

Am 17.02.2019 um 17:48 schrieb Greg Kroah-Hartman: On Sun, Feb 17, 2019 at 03:29:22PM +0100, Sebastian Gottschall wrote: according to user reports this patch will cause a serious regression. igmp snooping is not working anymore with this patch Am 02.11.2018 um 19:34 schrieb Greg Kroah

Re: [PATCH 4.19 01/24] bridge: do not add port to router list when receives query with source 0.0.0.0

according to user reports this patch will cause a serious regression. igmp snooping is not working anymore with this patch Am 02.11.2018 um 19:34 schrieb Greg Kroah-Hartman: 4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu [

Re: [PATCH 4.4 00/48] 4.4.162-stable review

4.4, 4.9 and 4.14 contain a new file named arch/riscv/include/asm/asm-prototypes.h this doesnt seem to belong to these kernels since arch/riscv was not even present before Sebastian Am 18.10.2018 um 19:54 schrieb Greg Kroah-Hartman: This is the start of the stable review cycle for the

Re: [PATCH 4.4 00/48] 4.4.162-stable review

4.4, 4.9 and 4.14 contain a new file named arch/riscv/include/asm/asm-prototypes.h this doesnt seem to belong to these kernels since arch/riscv was not even present before Sebastian Am 18.10.2018 um 19:54 schrieb Greg Kroah-Hartman: This is the start of the stable review cycle for the

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 22:42 schrieb Linus Torvalds: It would definitely be helpful, since I'm already quite busy with the normal merge window work. Having the embargo for L1TF end just as the merge window opened wasn't all that convenient. all good so far. i checked them all and i will see how

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 22:42 schrieb Linus Torvalds: It would definitely be helpful, since I'm already quite busy with the normal merge window work. Having the embargo for L1TF end just as the merge window opened wasn't all that convenient. all good so far. i checked them all and i will see how

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 21:42 schrieb Linus Torvalds: On Wed, Aug 15, 2018 at 12:26 PM Guenter Roeck wrote: Also seen in mainline. Meaning my non-SMP test builds are broken. Hmm. Grr. I think it's due mainly due to commit 447ae3166702 ("x86: Don't include linux/irq.h from asm/hardirq.h"), which

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 21:42 schrieb Linus Torvalds: On Wed, Aug 15, 2018 at 12:26 PM Guenter Roeck wrote: Also seen in mainline. Meaning my non-SMP test builds are broken. Hmm. Grr. I think it's due mainly due to commit 447ae3166702 ("x86: Don't include linux/irq.h from asm/hardirq.h"), which

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 20:55 schrieb Guenter Roeck: On Wed, Aug 15, 2018 at 08:27:00PM +0200, Sebastian Gottschall wrote: if i fix the other error (can be reproduced with disable smp on standard i386 build) another raises up again related to smp. to be serious. this patchset of x86 patches

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 20:55 schrieb Guenter Roeck: On Wed, Aug 15, 2018 at 08:27:00PM +0200, Sebastian Gottschall wrote: if i fix the other error (can be reproduced with disable smp on standard i386 build) another raises up again related to smp. to be serious. this patchset of x86 patches

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 20:26 schrieb Linus Torvalds: On Wed, Aug 15, 2018 at 11:22 AM Sebastian Gottschall wrote: btw. i found another compile error with x86 :-) This should already be fixed by commit d0055f351e64 ("x86/smp: fix non-SMP broken build due to redefin

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 20:26 schrieb Linus Torvalds: On Wed, Aug 15, 2018 at 11:22 AM Sebastian Gottschall wrote: btw. i found another compile error with x86 :-) This should already be fixed by commit d0055f351e64 ("x86/smp: fix non-SMP broken build due to redefin

Re: [PATCH 4.9 000/107] 4.9.120-stable review

-declaration]   amd_get_topology_early(c);   ^~   cpu_smt_check_topology_early Am 15.08.2018 um 19:52 schrieb Sven Joachim: On 2018-08-15 19:01 +0200, Sebastian Gottschall wrote: nother issue seen on xscale and as it affects all non SMP configured kernels kernel/cpu.c: In function

Re: [PATCH 4.9 000/107] 4.9.120-stable review

-declaration]   amd_get_topology_early(c);   ^~   cpu_smt_check_topology_early Am 15.08.2018 um 19:52 schrieb Sven Joachim: On 2018-08-15 19:01 +0200, Sebastian Gottschall wrote: nother issue seen on xscale and as it affects all non SMP configured kernels kernel/cpu.c: In function

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 19:52 schrieb Sven Joachim: On 2018-08-15 19:01 +0200, Sebastian Gottschall wrote: nother issue seen on xscale and as it affects all non SMP configured kernels kernel/cpu.c: In function 'boot_cpu_hotplug_init': kernel/cpu.c:2204:28: error: 'struct cpuhp_cpu_state' has

Re: [PATCH 4.9 000/107] 4.9.120-stable review

Am 15.08.2018 um 19:52 schrieb Sven Joachim: On 2018-08-15 19:01 +0200, Sebastian Gottschall wrote: nother issue seen on xscale and as it affects all non SMP configured kernels kernel/cpu.c: In function 'boot_cpu_hotplug_init': kernel/cpu.c:2204:28: error: 'struct cpuhp_cpu_state' has

Re: [PATCH 4.9 000/107] 4.9.120-stable review

nother issue seen on xscale and as it affects all non SMP configured kernels kernel/cpu.c: In function 'boot_cpu_hotplug_init': kernel/cpu.c:2204:28: error: 'struct cpuhp_cpu_state' has no member named 'booted_once'   this_cpu_write(cpuhp_state.booted_once, true); Am 14.08.2018 um 19:16

Re: [PATCH 4.9 000/107] 4.9.120-stable review

nother issue seen on xscale and as it affects all non SMP configured kernels kernel/cpu.c: In function 'boot_cpu_hotplug_init': kernel/cpu.c:2204:28: error: 'struct cpuhp_cpu_state' has no member named 'booted_once'   this_cpu_write(cpuhp_state.booted_once, true); Am 14.08.2018 um 19:16

Re: [PATCH 4.9 000/107] 4.9.120-stable review

if SWAP is disabled in kernel config, the following compile error will raise up with this release arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1): undefined reference to `generic_max_swapfile_size' of course this is simple to fix. the function max_swapfile_size must be

Re: [PATCH 4.9 000/107] 4.9.120-stable review

if SWAP is disabled in kernel config, the following compile error will raise up with this release arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1): undefined reference to `generic_max_swapfile_size' of course this is simple to fix. the function max_swapfile_size must be

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 31.05.2018 um 18:57 schrieb Bjorn Andersson: On Thu 31 May 04:45 PDT 2018, Greg Kroah-Hartman wrote: On Thu, May 31, 2018 at 01:21:56PM +0200, Sebastian Gottschall wrote: Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 31.05.2018 um 18:57 schrieb Bjorn Andersson: On Thu 31 May 04:45 PDT 2018, Greg Kroah-Hartman wrote: On Thu, May 31, 2018 at 01:21:56PM +0200, Sebastian Gottschall wrote: Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 31.05.2018 um 14:12 schrieb Greg Kroah-Hartman: On Thu, May 31, 2018 at 06:55:55AM -0500, Timur Tabi wrote: On 5/31/18 6:53 AM, Sebastian Gottschall wrote: i checked initially 4.9 with latest patches and 4.14 and reverted this line to get back to the old behaviour but a which view

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 31.05.2018 um 14:12 schrieb Greg Kroah-Hartman: On Thu, May 31, 2018 at 06:55:55AM -0500, Timur Tabi wrote: On 5/31/18 6:53 AM, Sebastian Gottschall wrote: i checked initially 4.9 with latest patches and 4.14 and reverted this line to get back to the old behaviour but a which view

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 31.05.2018 um 13:45 schrieb Greg Kroah-Hartman: On Thu, May 31, 2018 at 01:21:56PM +0200, Sebastian Gottschall wrote: Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 31.05.2018 um 13:45 schrieb Greg Kroah-Hartman: On Thu, May 31, 2018 at 01:21:56PM +0200, Sebastian Gottschall wrote: Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson [ Upstream commit a7aa75a2a7dba32594291a71c3704000a2fd7089 ] The base of the TLMM gpiochip should not be statically

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson [ Upstream commit a7aa75a2a7dba32594291a71c3704000a2fd7089 ] The base of the TLMM gpiochip should not be statically

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

of the network doesnt work anymore. this works for local multicast addresses, but not for neighbor networks which are using the routing table but correct me if i'm wrong -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

of the network doesnt work anymore. this works for local multicast addresses, but not for neighbor networks which are using the routing table but correct me if i'm wrong -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 16:25 schrieb David Miller: From: Sebastian Gottschall <s.gottsch...@dd-wrt.com> Date: Tue, 16 Jan 2018 04:50:39 +0100 please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 16:25 schrieb David Miller: From: Sebastian Gottschall Date: Tue, 16 Jan 2018 04:50:39 +0100 please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the issue. Then should

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

address -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: s.gottsch...@dd

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

address -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.dd-wrt.com email: s.gottsch...@dd

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

is being cleared to 0.0.0.0 in your configuration? you mean something like dumpstack and watching the flood comes over me? -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

is being cleared to 0.0.0.0 in your configuration? you mean something like dumpstack and watching the flood comes over me? -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 06:55 schrieb Greg Kroah-Hartman: On Tue, Jan 16, 2018 at 04:50:39AM +0100, Sebastian Gottschall wrote: please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the issue. So Linus's

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 06:55 schrieb Greg Kroah-Hartman: On Tue, Jan 16, 2018 at 04:50:39AM +0100, Sebastian Gottschall wrote: please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the issue. So Linus's

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

3.18 and 4.4 is affected too Am 16.01.2018 um 04:50 schrieb Sebastian Gottschall: please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the issue. Sebastian Am 01.01.2018 um 15:32 schrieb Greg

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

3.18 and 4.4 is affected too Am 16.01.2018 um 04:50 schrieb Sebastian Gottschall: please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the issue. Sebastian Am 01.01.2018 um 15:32 schrieb Greg

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 05:32 schrieb Kevin Cernekee: On Mon, Jan 15, 2018 at 8:26 PM, Sebastian Gottschall <s.gottsch...@dd-wrt.com> wrote: havent check the source addresses right now. i basicly discovered that this patch breaks the igmp routing and all traffic stops this here is from a w

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 05:32 schrieb Kevin Cernekee: On Mon, Jan 15, 2018 at 8:26 PM, Sebastian Gottschall wrote: havent check the source addresses right now. i basicly discovered that this patch breaks the igmp routing and all traffic stops this here is from a working system with the reverted patch

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 04:58 schrieb Kevin Cernekee: On Mon, Jan 15, 2018 at 7:50 PM, Sebastian Gottschall <s.gottsch...@dd-wrt.com> wrote: please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

Am 16.01.2018 um 04:58 schrieb Kevin Cernekee: On Mon, Jan 15, 2018 at 7:50 PM, Sebastian Gottschall wrote: please revert that on 4.9 and 4.14 it breaks igmp routing. it can be reproduced with any iptv connection using igmp-proxy. reverting this patch fixes the issue. Hi Sebastian

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

l4.daddr; - pip->saddr= fl4.saddr; + pip->saddr= igmpv3_get_srcaddr(dev, ); pip->protocol = IPPROTO_IGMP; pip->tot_len = 0; /* filled in later */ ip_select_ident(net, skb, NULL); -- Mit freundlichen Grüssen / Regards Sebastian Gottschal

Re: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

MP; pip->tot_len = 0; /* filled in later */ ip_select_ident(net, skb, NULL); -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäft

Re: 4.14.9 doesn't boot (regression)

at boot w/op any messages. Similar picture at the desktop. Both are stable Gentoo Linux hardened systems. This issue seems to exist in mainline too, probably visible with d120cd749 (stable) and 9aaefe7b59 (upstream). -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET

Re: 4.14.9 doesn't boot (regression)

at boot w/op any messages. Similar picture at the desktop. Both are stable Gentoo Linux hardened systems. This issue seems to exist in mainline too, probably visible with d120cd749 (stable) and 9aaefe7b59 (upstream). -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET

Re: [PATCH 3.18 00/64] 3.18.88-stable review

| 1 + security/keys/request_key.c | 46 +--- sound/core/pcm.c | 2 + sound/core/seq/seq_timer.c | 2 +- sound/usb/mixer.c| 13 +++-- tools/hv/hv_kvp_daemon.c

Re: [PATCH 3.18 00/64] 3.18.88-stable review

ss.c| 6 +- 61 files changed, 288 insertions(+), 200 deletions(-) -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Stein

Re: Linux 4.9.69

ignore the report. cause was a private driver fault which was triggered by the update Am 14.12.2017 um 22:07 schrieb Sebastian Gottschall: Am 14.12.2017 um 21:01 schrieb Greg KH: On Thu, Dec 14, 2017 at 08:20:08PM +0100, Sebastian Gottschall wrote: this happend with the rc1 version. dont know

Re: Linux 4.9.69

ignore the report. cause was a private driver fault which was triggered by the update Am 14.12.2017 um 22:07 schrieb Sebastian Gottschall: Am 14.12.2017 um 21:01 schrieb Greg KH: On Thu, Dec 14, 2017 at 08:20:08PM +0100, Sebastian Gottschall wrote: this happend with the rc1 version. dont know

Re: Linux 4.9.69

Am 14.12.2017 um 21:01 schrieb Greg KH: On Thu, Dec 14, 2017 at 08:20:08PM +0100, Sebastian Gottschall wrote: this happend with the rc1 version. dont know if it still applies, will check now. 4.9.68 works [    2.523730] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.69-rc1 #16 [    2.523823

Re: Linux 4.9.69

Am 14.12.2017 um 21:01 schrieb Greg KH: On Thu, Dec 14, 2017 at 08:20:08PM +0100, Sebastian Gottschall wrote: this happend with the rc1 version. dont know if it still applies, will check now. 4.9.68 works [    2.523730] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.69-rc1 #16 [    2.523823

Re: Linux 4.9.69

sctp_sendmsg sctp: use the right sk after waking up from wait_buf sleep Yoshihiro Shimoda (1): usb: gadget: udc: renesas_usb3: fix number of the pipes weiping zhang (1): virtio: release virtio index when fail to device_register -- Mit freundlichen Grüssen / Regards Sebast

Re: Linux 4.9.69

sctp_sendmsg sctp: use the right sk after waking up from wait_buf sleep Yoshihiro Shimoda (1): usb: gadget: udc: renesas_usb3: fix number of the pipes weiping zhang (1): virtio: release virtio index when fail to device_register -- Mit freundlichen Grüssen / Regards Sebast

Re: Linux 3.10.108 (EOL)

problem with all the drivers i have to rewrite for bsd and the bsd wireless stack is simply shit its basicly a impossible task. and most of my code is gpl licensed. mmh mixing with bsd code, not a good idea -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedi

Re: Linux 3.10.108 (EOL)

problem with all the drivers i have to rewrite for bsd and the bsd wireless stack is simply shit its basicly a impossible task. and most of my code is gpl licensed. mmh mixing with bsd code, not a good idea -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedi

Re: Linux 3.10.108 (EOL)

Am 15.11.2017 um 05:32 schrieb Willy Tarreau: On Tue, Nov 14, 2017 at 11:40:31PM +0100, Sebastian Gottschall wrote: And anyway the end of life has been indicated on kernel.org for 18 months and in every announce in 2017, so it cannot be a surprize anymore :-) At least nobody seemed to complain

Re: Linux 3.10.108 (EOL)

Am 15.11.2017 um 05:32 schrieb Willy Tarreau: On Tue, Nov 14, 2017 at 11:40:31PM +0100, Sebastian Gottschall wrote: And anyway the end of life has been indicated on kernel.org for 18 months and in every announce in 2017, so it cannot be a surprize anymore :-) At least nobody seemed to complain

Re: Linux 3.10.108 (EOL)

Am 14.11.2017 um 23:18 schrieb Willy Tarreau: On Tue, Nov 14, 2017 at 11:00:46PM +0100, Sebastian Gottschall wrote: Am 05.11.2017 um 08:46 schrieb Willy Tarreau: On Sun, Nov 05, 2017 at 06:59:48AM +, Harsh Shandilya wrote: Is this not pushed yet? I only see 3.10.107 Now

Re: Linux 3.10.108 (EOL)

Am 14.11.2017 um 23:18 schrieb Willy Tarreau: On Tue, Nov 14, 2017 at 11:00:46PM +0100, Sebastian Gottschall wrote: Am 05.11.2017 um 08:46 schrieb Willy Tarreau: On Sun, Nov 05, 2017 at 06:59:48AM +, Harsh Shandilya wrote: Is this not pushed yet? I only see 3.10.107 Now

Re: Linux 3.10.108 (EOL)

. Willy even if EOL has to come once for sure, its the last kernel which can be used on certain devices (embedded) since the kernel is growing bigger and bigger and wont run good anymore with limited resource Sebastian -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia

Re: Linux 3.10.108 (EOL)

. Willy even if EOL has to come once for sure, its the last kernel which can be used on certain devices (embedded) since the kernel is growing bigger and bigger and wont run good anymore with limited resource Sebastian -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia

Re: [PATCH 4.9 00/87] 4.9.62-stable review --> crash

Am 14.11.2017 um 08:41 schrieb Greg Kroah-Hartman: On Tue, Nov 14, 2017 at 07:48:47AM +0100, Sebastian Gottschall wrote: ahm it compiles well. but [   24.838120] Unable to handle kernel NULL pointer dereference at virtual address 0055 [   24.846193] pgd = c0004000 [   24.848893] [0055

Re: [PATCH 4.9 00/87] 4.9.62-stable review --> crash

Am 14.11.2017 um 08:41 schrieb Greg Kroah-Hartman: On Tue, Nov 14, 2017 at 07:48:47AM +0100, Sebastian Gottschall wrote: ahm it compiles well. but [   24.838120] Unable to handle kernel NULL pointer dereference at virtual address 0055 [   24.846193] pgd = c0004000 [   24.848893] [0055

Re: [PATCH 4.9 00/87] 4.9.62-stable review --> crash

| 28 - security/apparmor/lsm.c| 2 +- security/keys/trusted.c| 71 +-- sound/core/seq/oss/seq_oss_midi.c | 4 +- sound/core/seq/oss/seq_oss_readq.c | 29 + sound/core/seq/

Re: [PATCH 4.9 00/87] 4.9.62-stable review --> crash

ged, 722 insertions(+), 493 deletions(-) -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Stubenwaldallee 21a, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele

Re: [PATCH 4.4 08/40] ARM: dts: mvebu: pl310-cache disable double-linefill

- arm,double-linefill-incr = <1>; + arm,double-linefill-incr = <0>; arm,double-linefill-wrap = <0>; - arm,double-linefill = <1>; +

Re: [PATCH 4.4 08/40] ARM: dts: mvebu: pl310-cache disable double-linefill

ble-linefill-wrap = <0>; - arm,double-linefill = <1>; + arm,double-linefill = <0>; prefetch-data = <1>; }; -- Mit freundlichen Grüssen / Regards Sebastian Go

Re: hung task in mac80211

); void ieee80211_process_delba(struct ieee80211_sub_if_data *sdata, johannes I confirm that this patch fixes the hang too. I'm curious to see if there are noticeable performance differences between the two solutions. Cheers, -- Mit freundlichen Grüssen / Regards Sebastian Gottschall

Re: hung task in mac80211

rocess_delba(struct ieee80211_sub_if_data *sdata, johannes I confirm that this patch fixes the hang too. I'm curious to see if there are noticeable performance differences between the two solutions. Cheers, -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmen

Re: hung task in mac80211

that explans the behaviour i have found with latest mac80211 and ath10k. -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Berliner Ring 101, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter

Re: hung task in mac80211

that explans the behaviour i have found with latest mac80211 and ath10k. -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Berliner Ring 101, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter

Re: [PATCH 2/3] ath10k: use size_t for len variables

len; u8 spectral_count; mutex_lock(>conf_mutex); @@ -422,7 +422,8 @@ static ssize_t read_file_spectral_bins(struct file *file, { struct ath10k *ar = file->private_data; char buf[32]; - unsigned int len, bins, fft_size, bin_scale; + unsigned int bins

Re: [PATCH 2/3] ath10k: use size_t for len variables

mutex_lock(>conf_mutex); @@ -422,7 +422,8 @@ static ssize_t read_file_spectral_bins(struct file *file, { struct ath10k *ar = file->private_data; char buf[32]; - unsigned int len, bins, fft_size, bin_scale; + unsigned int bins, fft_size, bin_scale; + size

Re: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-ad...@xenproject.org: [Xen-devel] [linux-4.1 bisection] complet

or several days and I am not sure who is his backup. For the time being I would just suggest doing a local revert or apply Steven's patch from http://www.spinics.net/lists/stable/msg138760.html i patched it it locally and it resolved the issue in 3.18 -- Mit freundlichen Grüssen / Regards

Re: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-ad...@xenproject.org: [Xen-devel] [linux-4.1 bisection] complet

or several days and I am not sure who is his backup. For the time being I would just suggest doing a local revert or apply Steven's patch from http://www.spinics.net/lists/stable/msg138760.html i patched it it locally and it resolved the issue in 3.18 -- Mit freundlichen Grüssen / Regards

Re: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-ad...@xenproject.org: [Xen-devel] [linux-4.1 bisection] complet

o at http://vger.kernel.org/majordomo-info.html -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Berliner Ring 101, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.

Re: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-ad...@xenproject.org: [Xen-devel] [linux-4.1 bisection] complet

o at http://vger.kernel.org/majordomo-info.html -- Mit freundlichen Grüssen / Regards Sebastian Gottschall / CTO NewMedia-NET GmbH - DD-WRT Firmensitz: Berliner Ring 101, 64625 Bensheim Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele http://www.

arm: ARM_VIRT_EXT is not supported by all v7 platforms, so it should not be enabled by default

introduced in kernel 3.9 CONFIG_ARM_VIRT_EXT is default for all V7 arm cpu's. this is wrong and breaks smp support on BCM4708 for example. so keep it optional since no all v7 cpu's seem to support it. BCM4708 for instance is a arm cortex-a9. please merge this into one of the next patches.

arm: ARM_VIRT_EXT is not supported by all v7 platforms, so it should not be enabled by default

introduced in kernel 3.9 CONFIG_ARM_VIRT_EXT is default for all V7 arm cpu's. this is wrong and breaks smp support on BCM4708 for example. so keep it optional since no all v7 cpu's seem to support it. BCM4708 for instance is a arm cortex-a9. please merge this into one of the next patches.

  1   2   >