Re: hwmon.c as a kernel module in 3.18

was 'y' whereas CONFIG_HWMON was 'm'. I have fixed it now. thanks ani On Tue, May 24, 2016 at 1:10 PM, Ani Sinha wrote: > Hi guys : > > I am facing this interesting issue and I can't quite figure out what > the root cause is. Any help will be greatly app

hwmon.c as a kernel module in 3.18

Hi guys : I am facing this interesting issue and I can't quite figure out what the root cause is. Any help will be greatly appreciated. In my old 3.4 kernel, I had configured HWMON (CONFIG_HWMON) as a module ('m'). Now I am trying to upgrade to 3.18 and I am trying to keep the same kernel configu

Isn't 4.4 long term stable?

Hey guys, kernel.org lists linux 4.4.1 as "stable" but the releases page lists it as a long term stable kernel. Which one is true? thanks ani

Re: [PATCH 1/1] Fix 'sleeping function called from invalid context' warning in sysrq generated crash.

On Fri, Dec 18, 2015 at 5:01 AM, Paul E. McKenney wrote: > On Thu, Dec 17, 2015 at 05:15:10PM -0800, Ani Sinha wrote: >> Commit 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq") >> replaced spin_lock_irqsave() calls with >> rcu_read_lock() calls in sysrq. Since rcu_

Re: new warning on sysrq kernel crash trigger

On Thu, Dec 17, 2015 at 9:28 AM, Greg KH wrote: > On Wed, Dec 16, 2015 at 11:25:21AM -0500, Rik van Riel wrote: >> On 12/15/2015 07:52 PM, Ani Sinha wrote: >> > Rik, should I send a separate email with the patch or you are OK >> > with what I sent in the email? Are y

[PATCH 1/1] Fix 'sleeping function called from invalid context' warning in sysrq generated crash.

e we crash. Tested this patch on linux 3.18 by booting off one of our boards. Fixes: 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq") Signed-off-by: Ani Sinha --- drivers/tty/sysrq.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/tty/sysrq.c b/drivers/tty/sysrq.c in

Re: new warning on sysrq kernel crash trigger

Rik, should I send a separate email with the patch or you are OK with what I sent in the email? Are you queueing up my patch for applying upstream? On Tue, Dec 15, 2015 at 5:44 AM, Anirban Sinha wrote: > > > On Mon, 14 Dec 2015, Rik van Riel wrote: > >> On 12/14/2015 11:24 A

Re: new warning on sysrq kernel crash trigger

Rik, any comments? On Sat, Dec 12, 2015 at 6:33 AM, Paul E. McKenney wrote: > On Fri, Dec 11, 2015 at 04:16:37PM -0800, Ani Sinha wrote: >> On Fri, 11 Dec 2015, Paul E. McKenney wrote: >> > On Fri, Dec 11, 2015 at 05:10:43PM -0500, Rik van Riel wrote: >> > > On

Re: new warning on sysrq kernel crash trigger

On Fri, 11 Dec 2015, Paul E. McKenney wrote: > On Fri, Dec 11, 2015 at 05:10:43PM -0500, Rik van Riel wrote: > > On 12/11/2015 03:44 PM, Ani Sinha wrote: > > > > > > > > > On Thu, 10 Dec 2015, Paul E. McKenney wrote: > > > > > >>

Re: new warning on sysrq kernel crash trigger

r our old 3.4 kernel). I will send in a patch as per your former suggestion ... On Fri, Dec 11, 2015 at 4:02 PM, Paul E. McKenney wrote: > On Fri, Dec 11, 2015 at 03:41:04PM -0800, Ani Sinha wrote: >> On Fri, Dec 11, 2015 at 2:27 PM, Paul E. McKenney >> wrote: >> > On Fri

Re: new warning on sysrq kernel crash trigger

On Fri, Dec 11, 2015 at 2:27 PM, Paul E. McKenney wrote: > On Fri, Dec 11, 2015 at 05:10:43PM -0500, Rik van Riel wrote: >> On 12/11/2015 03:44 PM, Ani Sinha wrote: >> > >> > >> > On Thu, 10 Dec 2015, Paul E. McKenney wrote: >> > >> >>

Re: new warning on sysrq kernel crash trigger

On Thu, 10 Dec 2015, Paul E. McKenney wrote: > On Thu, Dec 10, 2015 at 03:57:09PM -0800, Ani Sinha wrote: > > Hi guys > > > > I am noticing a new warning in linux 3.18 which we did not see before > > in linux 3.4 : > > > > bash-4.1# echo c >

Re: new warning on sysrq kernel crash trigger

Well I can certainly send a patch but I wonder if simply using SRCU for this one instance in Rik's original patch will not break anything else. Rik, please provide your thoughts. On Thu, Dec 10, 2015 at 9:26 PM, Paul E. McKenney wrote: > On Thu, Dec 10, 2015 at 03:57:09PM -0800, Ani Sin

new warning on sysrq kernel crash trigger

Hi guys I am noticing a new warning in linux 3.18 which we did not see before in linux 3.4 : bash-4.1# echo c > /proc/sysrq-trigger [ 978.807185] BUG: sleeping function called from invalid context at ../arch/x86/mm/fault.c:1187 [ 978.909816] in_atomic(): 0, irqs_disabled(): 0, pid: 4706, name:

kernel_thread() for non-GPL drivers

Hi Al : I see that there has been some code re-org in linux 3.7 starting with commit 7076aada1040de4ed79a5977dbabdb5e5ea5e249 Author: Al Viro Date: Mon Sep 10 16:44:54 2012 -0400 x86: split ret_from_fork Signed-off-by: Al Viro This removed the kernel_thread() x86 specific function

Re: [PATCH 1/1] update ip-sysctl.txt documentation (v2)

On Wed, Jan 7, 2015 at 3:45 PM, Ani Sinha wrote: > Update documentation to reflect the fact that > /proc/sys/net/ipv4/route/max_size is no longer used for ipv4. Any more feedback on this? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

[PATCH 1/1] update ip-sysctl.txt documentation (v2)

Update documentation to reflect the fact that /proc/sys/net/ipv4/route/max_size is no longer used for ipv4. Signed-off-by: Ani Sinha --- Documentation/networking/ip-sysctl.txt |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/Documentation/networking/ip-sysctl.txt b

Re: [PATCH 1/1] update ip-sysctl.txt documentation

On Wed, Jan 7, 2015 at 2:11 AM, David Laight wrote: > From: Ani Sinha >> Update documentation to reflect the fact that >> /proc/sys/net/ipv4/route/max_size is no longer used for ipv4. >> >> Signed-off-by: Ani Sinha >> --- >> Documentation/networking/

Re: [PATCH 1/1] update ip-sysctl.txt documentation

On Tue, Jan 6, 2015 at 2:40 PM, David Miller wrote: > From: Ani Sinha > Date: Tue, 6 Jan 2015 14:33:45 -0800 > >> @@ -64,8 +64,10 @@ fwmark_reflect - BOOLEAN >> Default: 0 >> >> route/max_size - INTEGER >> - Maximum number of routes allowed in t

[PATCH 1/1] update ip-sysctl.txt documentation

Update documentation to reflect the fact that /proc/sys/net/ipv4/route/max_size is no longer used for ipv4. Signed-off-by: Ani Sinha --- Documentation/networking/ip-sysctl.txt |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/networking/ip-sysctl.txt b

[PATCH 1/1] update ip-sysctl.txt documentation

Update documentation to reflect the fact that /proc/sys/net/ipv4/route/max_size is no longer used for ipv4. Signed-off-by: Ani Sinha --- Documentation/networking/ip-sysctl.txt |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/networking/ip-sysctl.txt b

[PATCH 1/1] update ip-sysctl.txt documentation

Update documentation to reflect the fact that /proc/sys/net/ipv4/route/max_size is no longer used for ipv4. Signed-off-by: Ani Sinha --- Documentation/networking/ip-sysctl.txt |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/networking/ip-sysctl.txt b

print kernel version on the console during panic/oops

at sometimes it is not possible to get the whole crash log from /var/log/console. The console log is only what we have. Signed-off-by : Ani Sinha Index: linux-2.6.38/arch/x86/kernel/dumpstack.c === --- linux-2.6.38.orig/arc

RX/dropped counter values for tagged packets

hello everyone : Please bear with me if you think I said something wrong. I was looking at the netif_receive_skb() code and it seems to me that for vlan tagged packets, the counters are manipulated at two different places. One is from vlan_do_receive() where the receive counters are incremented.