[WARNING ]Re: related to fixing depreciated api

On Mon, Dec 14, 2020 at 10:12 PM Jeffrin Jose T wrote: > > hello, > > i have worked on to fix depreciated api issue from > tools/testing/selftests/intel_pstate/aerf.c > > i met with the following error related... > > --x--x-> > $pwd >

Re: [PATCH 5.8 000/633] 5.8.17-rc1 review

hello, Compiled and booted 5.8.17-rc1+. Looks like no typical regression or regressions. Tested-by: Jeffrin Jose T On Tue, Oct 27, 2020 at 8:23 PM Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.8.17 release. > There are 633 patches in this series, all

Re: [PATCH 4.14 000/191] 4.14.203-rc1 review

hello , compiled and booted 4.14.203-rc1+ . dmesg atleast throws issue or issues. -x--x--x---x- [1.822459] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND

Re: BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70

hello Kees, please mention me ... Reported-by: Jeffrin Jose T Tested-by: Jeffrin Jose T On Tue, Jul 30, 2019 at 1:25 AM Jens Axboe wrote: > > On 7/29/19 1:34 PM, Jeffrin Thalakkottoor wrote: > > hello Kees Cook, > > > > i tested your fix and i think it worked

Re: BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70

19 at 11:28:29AM -0700, Nick Desaulniers wrote: > > On Wed, Jul 10, 2019 at 10:44 AM Jeffrin Thalakkottoor > > wrote: > > > > > > hello all , > > > > > > i encountered a KASAN bug related .here are some related > > > informatio

Re: BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70

hello Jens Axboe, Please can you take a look at related code and also patch from Kees ? On Tue, Jul 16, 2019 at 11:58 PM Nick Desaulniers wrote: > > On Wed, Jul 10, 2019 at 10:44 AM Jeffrin Thalakkottoor > wrote: > > > > hello all , > > > > i encountered a KAS

BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70

hello all , i encountered a KASAN bug related .here are some related information... ---x-x-- [ 30.037312] BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70 [ 30.037447] Read of size 16 at addr

BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70

hello , [ 55.169278] == [ 55.169899] BUG: KASAN: global-out-of-bounds in ata_exec_internal_sg+0x50f/0xc70 [libata] [ 55.170039] Read of size 16 at addr c0723500 by task scsi_eh_1/149 [ 55.186354] The buggy address

Re: about selftests/rtc test related stuff

On Fri, May 24, 2019 at 4:22 AM Alexandre Belloni wrote: > I just sent a fix for that timeout issue. anyway thanks related to that shall i send a selftest fix that bail out in the test program if the user does not have root privileges ? -- software engineer rajagiri school of engineering and

Re: about selftests/rtc test related stuff

On Thu, May 23, 2019 at 11:17 PM Alexandre Belloni wrote: > Your user probably doesn't have access to the rtc device file. anyway thanks related Following is the result with sudo x--x $sudo ./rtctest

Re: [PATCH v2] selftests: netfilter: missing error check when setting up veth interface

Thanks to all ! On Tue, May 21, 2019 at 11:41 PM Pablo Neira Ayuso wrote: > > On Wed, May 15, 2019 at 12:14:04PM +0530, Jeffrin Jose T wrote: > > A test for the basic NAT functionality uses ip command which > > needs veth device.There is a condition where the kernel support > > for veth is not

Re: [PATCH] selftests : netfilter: Wrote a error and exit code for a command which needed veth kernel module.

Hi Pablo, Please follow up on the mail you sent. This is for my interest to see my patch upstream On Tue, Apr 30, 2019 at 4:22 PM Pablo Neira Ayuso wrote: > > Cc'ing netfilter-de...@vger.kernel.org > > On Tue, Apr 30, 2019 at 12:02:56PM +0200, Florian Westphal wrote: > > shuah wrote: > > >

Re: [PATCH] selftests : netfilter: Wrote a error and exit code for a command which needed veth kernel module.

Hello Shuah, did you get the mail related stuff below ? On Fri, Apr 5, 2019 at 10:17 PM Florian Westphal wrote: > > Jeffrin Jose T wrote: > > A test for the basic NAT functionality uses ip command which > > needs veth device.There is a condition where the kernel support > > for veth is not

Re: about selftests/netfilter test related issue

let me also work on that too. anyway thanks On Tue, Apr 2, 2019 at 1:46 AM Florian Westphal wrote: > > Jeffrin Thalakkottoor wrote: > > Error: Unknown device type. > > Feel free to send a patch that makes it display a more reasonable > exit+error here. -- software eng

Re: about selftests/netfilter test related issue

anyway thanks for the reply. let me look on what you said and learn On Tue, Apr 2, 2019 at 1:15 AM Florian Westphal wrote: > > Jeffrin Thalakkottoor wrote: > > i think the script nft_nat.sh is assuming devices eth0 and eth1 > > No it does not. > These are arbitrary names

about selftests/netfilter test related issue

hello i think the script nft_nat.sh is assuming devices eth0 and eth1 which may not be the case always. my suggestion is why not give the needed network devices as arguments to the script. iam showing related command line sessions below and error related file is attached.

Re: [PATCH v2] error message found related

> Your subject is too long. ok . i have changed it > Please upgrade bash? anyway now i have an upgraded one. here is a clipping related to the error -x---x Thu Feb 14 23:49:13 IST 2019 Running test: kmod_test_0007 - run #4 kmod_test_0005: OK!

Fwd: [PATCH] selftests: kmod: worked on errors which breaks the overall execution of the test script

-- Forwarded message - From: Jeffrin Thalakkottoor Date: Mon, Jan 28, 2019 at 11:33 PM Subject: Re: [PATCH] selftests: kmod: worked on errors which breaks the overall execution of the test script To: Luis Chamberlain Cc: Shuah Khan , lkml , , Andrew Morton > > o

Re: [RESEND PATCH] selftests: intel_pstate: notification about privilege required to run intel_pstate testing script

On Thu, May 31, 2018 at 5:12 AM, Shuah Khan wrote: > I will take this patch and apply it to linux-kselftest next for 4.18-rc1. anyway thanks . > For next time, this patch should have been tagged v2 not RESEND. Also please > include changes made since the last version in this spot after the >

Re: [RESEND PATCH] selftests: intel_pstate: notification about privilege required to run intel_pstate testing script

On Thu, May 31, 2018 at 5:12 AM, Shuah Khan wrote: > I will take this patch and apply it to linux-kselftest next for 4.18-rc1. anyway thanks . > For next time, this patch should have been tagged v2 not RESEND. Also please > include changes made since the last version in this spot after the >

Re: [PATCH] selftests: intel_pstate: Fixes for the testing script for Intel P-State driver

On Thu, May 24, 2018 at 10:11 PM, Shuah Khan wrote: > The commit log doesn't match the commit summary. Please rephrase both the > commit summary and log to indicate why this fix is necessary. i will work related to that > Odd. I don't see your patch posted on the

Re: [PATCH] selftests: intel_pstate: Fixes for the testing script for Intel P-State driver

On Thu, May 24, 2018 at 10:11 PM, Shuah Khan wrote: > The commit log doesn't match the commit summary. Please rephrase both the > commit summary and log to indicate why this fix is necessary. i will work related to that > Odd. I don't see your patch posted on the linux-kselftest patchwork and

TEST mail

hello

TEST mail

hello

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

> Oh ... one more thing. Did your e-mail client line wrap that last line? > >> mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1526932210 SOCKET 0 APIC >> 0 microcode 2a > > That should all be on one line. Sorry IF ANY Problem anyway i send the message using gmail with plain text mode -- software

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

> Oh ... one more thing. Did your e-mail client line wrap that last line? > >> mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1526932210 SOCKET 0 APIC >> 0 microcode 2a > > That should all be on one line. Sorry IF ANY Problem anyway i send the message using gmail with plain text mode -- software

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

On Tue, May 22, 2018 at 2:27 AM, Luck, Tony wrote: > How about this: > > $ sudo dmesg -r | grep -C 30 Bank > > -Tony --> $sudo dmesg -r | grep -C 30 Bank x2apic: IRQ remapping doesn't support

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

On Tue, May 22, 2018 at 2:27 AM, Luck, Tony wrote: > How about this: > > $ sudo dmesg -r | grep -C 30 Bank > > -Tony --> $sudo dmesg -r | grep -C 30 Bank x2apic: IRQ remapping doesn't support X2APIC mode ..TIMER:

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

> (*) Can you send a snip from the raw dmesg output that starts > a couple of lines before: > > > ... [Hardware Error]: CPU 0: Machine Check: 0 Bank: 5 ... > > and continues a couple of lines past > > ... [Hardware Error]: PROCESSOR 0:306d4 ... > > and I'll take a look at why

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

> (*) Can you send a snip from the raw dmesg output that starts > a couple of lines before: > > > ... [Hardware Error]: CPU 0: Machine Check: 0 Bank: 5 ... > > and continues a couple of lines past > > ... [Hardware Error]: PROCESSOR 0:306d4 ... > > and I'll take a look at why

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

> Ok, but please do not top-post. Ok > Looks like mcelog has trouble decoding this. Have you updated mcelog to > the latest version in your distro? . mcelog 153+dfsg-1 -- software engineer rajagiri school of engineering and technology

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

> Ok, but please do not top-post. Ok > Looks like mcelog has trouble decoding this. Have you updated mcelog to > the latest version in your distro? . mcelog 153+dfsg-1 -- software engineer rajagiri school of engineering and technology

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

ANGE): eth0: link becomes ready Bluetooth: hci0: command 0x1003 tx timeout IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initial

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

hci0: command 0x1003 tx timeout IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 fuse init (API version 7.26) rfkill: input handler disabled r8169 :02:00.0 eth0: link down r8169 :0

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

ignore this "i did not find this message in a typical 4.9.x kernel" line On Sun, May 20, 2018 at 4:05 PM, Jeffrin Thalakkottoor <jeff...@rajagiritech.edu.in> wrote: > as far as i know , may be there is not much change in system behavior. > i just found these messages du

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

ignore this "i did not find this message in a typical 4.9.x kernel" line On Sun, May 20, 2018 at 4:05 PM, Jeffrin Thalakkottoor wrote: > as far as i know , may be there is not much change in system behavior. > i just found these messages during boot time > i did no

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

D (20180313/psargs-330) -> On Mon, May 14, 2018 at 10:20 PM, Luck, Tony <tony.l...@intel.com> wrote: > On Mon, May 14, 2018 at 06:27:52PM +0200, Borislav Petkov wrote: >> On Mon, May 14, 2018 at 09:19

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

80313/psargs-330) -> On Mon, May 14, 2018 at 10:20 PM, Luck, Tony wrote: > On Mon, May 14, 2018 at 06:27:52PM +0200, Borislav Petkov wrote: >> On Mon, May 14, 2018 at 09:19:11PM +0530, Jeffrin Thalakkottoor wrote: >>

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

t 5:20 PM, Jeffrin Thalakkottoor > <jeff...@rajagiritech.edu.in> wrote: >> hello , >> >> the error from "dmesg -l err" related ... >> >> -> >> >&g

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

as far as i know , may be there is not much change in system behavior. i just found these messages during boot time i did not find this message in a typical 4.9.x kernel On Mon, May 14, 2018 at 4:04 AM, Andy Shevchenko wrote: > On Sun, May 13, 2018 at 5:20 PM, Jeffrin Thalakkottoor >

PROBLEM: found 2 tests failed using "perf test" command

hello, i found two tests failed while i did "sudo ./perf test" ---> 24: Object code reading : FAILED! 64: probe libc's inet_pton & backtrace it with ping : FAILED!

PROBLEM: found 2 tests failed using "perf test" command

hello, i found two tests failed while i did "sudo ./perf test" ---> 24: Object code reading : FAILED! 64: probe libc's inet_pton & backtrace it with ping : FAILED!

PROBLEM: mce: [Hardware Error] from dmesg -l emerg

hello, output related of "sudo dmesg -l emerg" from my laptop... ---> $sudo dmesg -l emerg [sudo] password for jeffrin: [0.041023] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5:

PROBLEM: mce: [Hardware Error] from dmesg -l emerg

hello, output related of "sudo dmesg -l emerg" from my laptop... ---> $sudo dmesg -l emerg [sudo] password for jeffrin: [0.041023] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5:

PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

hello , the error from "dmesg -l err" related ... -> [1.709950] ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20180313/psargs-330) [1.710045] ACPI Error:

PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

hello , the error from "dmesg -l err" related ... -> [1.709950] ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20180313/psargs-330) [1.710045] ACPI Error:

Re: [PATCH] selftests: intel_pstate: Fix a condition which does not notify user that root permission is useful

thanks. i will work on... On Wed, May 9, 2018 at 11:54 PM, Daniel Díaz wrote: > Hello! > > > On 05/09/2018 12:38 PM, Jeffrin Jose T wrote: >> aperf program uses /dev/cpu which is normally a root only >> access area. so in that case to successfully run thet test, >> root

Re: [PATCH] selftests: intel_pstate: Fix a condition which does not notify user that root permission is useful

thanks. i will work on... On Wed, May 9, 2018 at 11:54 PM, Daniel Díaz wrote: > Hello! > > > On 05/09/2018 12:38 PM, Jeffrin Jose T wrote: >> aperf program uses /dev/cpu which is normally a root only >> access area. so in that case to successfully run thet test, >> root permissions are

Re: [PATCH] selftests:intel_pstate: fixes typical crash of a testing script for Intel P-State driver

hello Shuah, i had later send another version of that patch. anyway thank you daniel for your effort thank you both. On Wed, May 9, 2018 at 1:51 AM, Shuah Khan wrote: > On 05/04/2018 01:47 PM, Shuah Khan wrote: >> On 04/29/2018 01:12 PM, Jeffrin Jose T wrote: >>>

Re: [PATCH] selftests:intel_pstate: fixes typical crash of a testing script for Intel P-State driver

hello Shuah, i had later send another version of that patch. anyway thank you daniel for your effort thank you both. On Wed, May 9, 2018 at 1:51 AM, Shuah Khan wrote: > On 05/04/2018 01:47 PM, Shuah Khan wrote: >> On 04/29/2018 01:12 PM, Jeffrin Jose T wrote: >>> Testing script for Intel

Re: PROBLEM: error due to conflicting types during build of kselftests

anyway my current is gcc (Debian 7.3.0-16) 7.3.0 may be you can try ... make -C tools/testing/selftests 2> error.txt On Sat, Apr 28, 2018 at 5:08 AM, Randy Dunlap <rdun...@infradead.org> wrote: > On 04/20/2018 11:03 AM, Jeffrin Thalakkottoor wrote: >> hello, >> >&

Re: PROBLEM: error due to conflicting types during build of kselftests

anyway my current is gcc (Debian 7.3.0-16) 7.3.0 may be you can try ... make -C tools/testing/selftests 2> error.txt On Sat, Apr 28, 2018 at 5:08 AM, Randy Dunlap wrote: > On 04/20/2018 11:03 AM, Jeffrin Thalakkottoor wrote: >> hello, >> >> the foll

Re: possible BUG: selftest about raw_skew failed

Skip 0 Error 0 1..0 ok 1..7 selftests: raw_skew [PASS] On Fri, Apr 27, 2018 at 1:11 PM, Miroslav Lichvar <mlich...@redhat.com> wrote: > On Thu, Apr 26, 2018 at 11:28:29PM +0200, Thomas Gleixner wrote: >> On Sat, 21 Apr 2018, Jeffrin Thalakkott

Re: possible BUG: selftest about raw_skew failed

Skip 0 Error 0 1..0 ok 1..7 selftests: raw_skew [PASS] On Fri, Apr 27, 2018 at 1:11 PM, Miroslav Lichvar wrote: > On Thu, Apr 26, 2018 at 11:28:29PM +0200, Thomas Gleixner wrote: >> On Sat, 21 Apr 2018, Jeffrin Thalakkottoor wrote: >> > selftests: raw_skew >> > ==

Re: possible BUG: selftest about raw_skew failed

I kind of ignored. i was not sure what that meant actually. On Fri, Apr 27, 2018 at 3:03 AM, John Stultz <john.stu...@linaro.org> wrote: > On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor > <jeff...@rajagiritech.edu.in> wrote: >> hello, >> >>

Re: possible BUG: selftest about raw_skew failed

I kind of ignored. i was not sure what that meant actually. On Fri, Apr 27, 2018 at 3:03 AM, John Stultz wrote: > On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor > wrote: >> hello, >> >> failure of a test in selftest:timers &

Re: possible BUG: selftests: proc-loadavg-001 failed during kernel testing

selftests: proc-loadavg-001 [PASS] Please add me in changelog if i was useful. On Sat, Apr 21, 2018 at 8:41 PM, Jeffrin Thalakkottoor <jeff...@rajagiritech.edu.in> wrote: > hello, > > selftests: proc-loadavg-001 > > not ok 1..1 selftes

Re: possible BUG: selftests: proc-loadavg-001 failed during kernel testing

selftests: proc-loadavg-001 [PASS] Please add me in changelog if i was useful. On Sat, Apr 21, 2018 at 8:41 PM, Jeffrin Thalakkottoor wrote: > hello, > > selftests: proc-loadavg-001 > > not ok 1..1 selftests: proc-loadavg-001 [FAIL] &

possible BUG: selftests: proc-loadavg-001 failed during kernel testing

hello, selftests: proc-loadavg-001 not ok 1..1 selftests: proc-loadavg-001 [FAIL] To reproduce : make -C tools/testing/selftests/proc run_tests Linux debian 4.17.0-rc1+ #3 SMP Sat Apr 21 03:41:44 IST 2018 x86_64 GNU/Linux GNU Make4.2.1

possible BUG: selftests: proc-loadavg-001 failed during kernel testing

hello, selftests: proc-loadavg-001 not ok 1..1 selftests: proc-loadavg-001 [FAIL] To reproduce : make -C tools/testing/selftests/proc run_tests Linux debian 4.17.0-rc1+ #3 SMP Sat Apr 21 03:41:44 IST 2018 x86_64 GNU/Linux GNU Make4.2.1

possible BUG: selftest about raw_skew failed

hello, failure of a test in selftest:timers selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 17.910(est) 16.820(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok

possible BUG: selftest about raw_skew failed

hello, failure of a test in selftest:timers selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 17.910(est) 16.820(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok

POSSIBLE BUG: boot gets stuck and loads initramfs shell

hello, i did a new git pull on my mainline linux kernel repository i did "make localmodconfig" and compiled i got a boot failure related. i got message about not able to mount filesystem. it then loaded the initramfs shell. i recompiled the kernel with ext4 file system inbuilt (i mean not as a

POSSIBLE BUG: boot gets stuck and loads initramfs shell

hello, i did a new git pull on my mainline linux kernel repository i did "make localmodconfig" and compiled i got a boot failure related. i got message about not able to mount filesystem. it then loaded the initramfs shell. i recompiled the kernel with ext4 file system inbuilt (i mean not as a

PROBLEM: error due to conflicting types during build of kselftests

hello, the following is the error found... --- protection_keys.c:421:5: error: conflicting types for ‘pkey_set’ int pkey_set(int pkey, unsigned long rights, unsigned long flags) ^~~~

PROBLEM: error due to conflicting types during build of kselftests

hello, the following is the error found... --- protection_keys.c:421:5: error: conflicting types for ‘pkey_set’ int pkey_set(int pkey, unsigned long rights, unsigned long flags) ^~~~

test mail

this is a test mail -- software engineer rajagiri school of engineering and technology

test mail

this is a test mail -- software engineer rajagiri school of engineering and technology