org.kernel.vger.smatch archive

430 archived articles, newest first (page 2 of 5). Latest articles →

Re: smatch regression - after recent update
Mon, 14 Oct 2024 13:41:28 +0300
Dan Carpenter <[email protected]> • #591
smatch regression - after recent update
Mon, 14 Oct 2024 15:54:34 +0530
Harshit Mogalapalli <[email protected]> • #590
check locking re-write
Mon, 14 Oct 2024 12:59:28 +0300
Dan Carpenter <[email protected]> • #589
Re: Question on a error handling related warning
Wed, 9 Oct 2024 14:05:24 +0300
Dan Carpenter <[email protected]> • #588
Question on a error handling related warning
Wed, 9 Oct 2024 11:15:04 +0530
Harshit Mogalapalli <[email protected]> • #587
Re: Bug-report: Smatch treats scoped_guard() as unreachable code ?
Tue, 20 Aug 2024 01:07:58 +0530
Harshit Mogalapalli <[email protected]> • #586
Re: Bug-report: Smatch treats scoped_guard() as unreachable code ?
Mon, 19 Aug 2024 22:29:37 +0300
Dan Carpenter <[email protected]> • #585
Bug-report: Smatch treats scoped_guard() as unreachable code ?
Tue, 20 Aug 2024 00:38:21 +0530
Harshit Mogalapalli <[email protected]> • #584
Re: FP with unreachable code check
Wed, 7 Aug 2024 07:23:28 -0500
Dan Carpenter <[email protected]> • #583
Re: False positive due to MACROs in nfsd code
Wed, 7 Aug 2024 07:19:17 -0500
Dan Carpenter <[email protected]> • #582
Re: min/max() changes
Wed, 7 Aug 2024 07:14:19 -0500
Dan Carpenter <[email protected]> • #581
FP with unreachable code check
Mon, 5 Aug 2024 14:55:52 +0530
Harshit Mogalapalli <[email protected]> • #580
Re: min/max() changes
Mon, 5 Aug 2024 14:38:44 +0530
Harshit Mogalapalli <[email protected]> • #579
Re: min/max() changes
Mon, 5 Aug 2024 14:17:42 +0530
Harshit Mogalapalli <[email protected]> • #578
False positive due to MACROs in nfsd code
Mon, 5 Aug 2024 11:51:01 +0530
Harshit Mogalapalli <[email protected]> • #577
Re: min/max() changes
Fri, 2 Aug 2024 22:34:29 +0530
Harshit Mogalapalli <[email protected]> • #576
Re: min/max() changes
Fri, 2 Aug 2024 12:00:28 -0500
Dan Carpenter <[email protected]> • #575
Re: min/max() changes
Fri, 2 Aug 2024 11:54:18 -0500
Dan Carpenter <[email protected]> • #574
Re: min/max() changes
Fri, 2 Aug 2024 11:46:14 -0500
Dan Carpenter <[email protected]> • #573
min/max() changes
Fri, 2 Aug 2024 11:41:05 -0500
Dan Carpenter <[email protected]> • #572
Re: Treat macro call like ordinary functions in smatch.
Mon, 1 Jul 2024 16:10:10 +0200
Dan Carpenter <[email protected]> • #571
Re: Treat macro call like ordinary functions in smatch.
Mon, 24 Jun 2024 13:50:57 +0800
Hongyi Lu <[email protected]> • #570
Re: Treat macro call like ordinary functions in smatch.
Thu, 20 Jun 2024 22:57:36 +0300
Dan Carpenter <[email protected]> • #569
Re: Treat macro call like ordinary functions in smatch.
Thu, 20 Jun 2024 17:39:04 +0300
Dan Carpenter <[email protected]> • #568
Re: Treat macro call like ordinary functions in smatch.
Thu, 20 Jun 2024 22:12:28 +0800
Hongyi Lu <[email protected]> • #567
Re: Treat macro call like ordinary functions in smatch.
Thu, 20 Jun 2024 15:33:09 +0300
Dan Carpenter <[email protected]> • #566
Re: [PATCH 0/2] Support custom build directory for kernel
Wed, 19 Jun 2024 10:36:50 +0300
Dan Carpenter <[email protected]> • #565
[PATCH 2/2] kernel: Add support for custom build directory
Tue, 18 Jun 2024 23:20:17 +0300
Cristian Ciocaltea <[email protected]> • #564
[PATCH 1/2] kchecker: Fix --outfile handling
Tue, 18 Jun 2024 23:20:16 +0300
Cristian Ciocaltea <[email protected]> • #563
[PATCH 0/2] Support custom build directory for kernel
Tue, 18 Jun 2024 23:20:15 +0300
Cristian Ciocaltea <[email protected]> • #562
Re: [PATCH] sentinel_ctltable: Add a check for sentinel elements in ctl_table arrays
Fri, 14 Jun 2024 16:28:52 +0300
Dan Carpenter <[email protected]> • #561
[PATCH] sentinel_ctltable: Add a check for sentinel elements in ctl_table arrays
Fri, 14 Jun 2024 14:29:41 +0200
Joel Granados via B4 Relay <[email protected]> • #560
Re: How do I make a contribution to the automatic analysis done on the kernel
Tue, 4 Jun 2024 17:48:38 +0200
Joel Granados <[email protected]> • #559
Re: How do I make a contribution to the automatic analysis done on the kernel
Tue, 4 Jun 2024 10:53:42 +0300
Dan Carpenter <[email protected]> • #558
How do I make a contribution to the automatic analysis done on the kernel
Mon, 3 Jun 2024 14:28:58 +0200
Joel Granados <[email protected]> • #557
Re: likely/unlikely usage validation
Wed, 29 May 2024 17:36:59 +0300
Dan Carpenter <[email protected]> • #556
Re: likely/unlikely usage validation
Wed, 29 May 2024 17:33:12 +0300
Dan Carpenter <[email protected]> • #555
Re: likely/unlikely usage validation
Wed, 29 May 2024 17:33:04 +0300
Dan Carpenter <[email protected]> • #554
Re: likely/unlikely usage validation
Wed, 29 May 2024 17:32:58 +0300
Dan Carpenter <[email protected]> • #553
Re: likely/unlikely usage validation
Wed, 29 May 2024 10:44:08 +0200
Rasmus Villemoes <[email protected]> • #552
Re: likely/unlikely usage validation
Tue, 28 May 2024 14:51:33 +0200
Rasmus Villemoes <[email protected]> • #551
Re: likely/unlikely usage validation
Tue, 28 May 2024 14:21:42 +0200
Mateusz Guzik <[email protected]> • #550
Re: likely/unlikely usage validation
Tue, 28 May 2024 14:03:26 +0200
Rasmus Villemoes <[email protected]> • #549
likely/unlikely usage validation
Tue, 28 May 2024 12:37:23 +0200
Mateusz Guzik <[email protected]> • #548
Re: [PATCH] pre-proc: use uname() syscall instead of invoking uname
Fri, 10 May 2024 20:41:44 +0300
Dan Carpenter <[email protected]> • #547
Re: [PATCH] pre-proc: use uname() syscall instead of invoking uname
Fri, 10 May 2024 18:18:57 +0300
Dan Carpenter <[email protected]> • #546
[PATCH] pre-proc: use uname() syscall instead of invoking uname
Fri, 10 May 2024 17:12:14 +0200
Andrey Albershteyn <[email protected]> • #545
Re: About building the database for smatch
Mon, 8 Apr 2024 08:42:49 +0300
Dan Carpenter <[email protected]> • #544
About building the database for smatch
Mon, 8 Apr 2024 12:29:56 +0800 (GMT+08:00)
李书畅 <[email protected]> • #543
Re: [PATCH 0/3] Documentation/smatch: RST conversion and fixes
Tue, 2 Apr 2024 17:33:32 +0300
Dan Carpenter <[email protected]> • #542
[PATCH 3/3] Documentation/smatch: fix typo in submitting-patches.md
Mon, 1 Apr 2024 22:45:12 +0200
Javier Carrasco <[email protected]> • #541
[PATCH 2/3] Documentation/smatch: convert to RST
Mon, 1 Apr 2024 22:45:11 +0200
Javier Carrasco <[email protected]> • #540
[PATCH 1/3] Documentation/smatch: fix paths in the examples
Mon, 1 Apr 2024 22:45:10 +0200
Javier Carrasco <[email protected]> • #539
[PATCH 0/3] Documentation/smatch: RST conversion and fixes
Mon, 1 Apr 2024 22:45:09 +0200
Javier Carrasco <[email protected]> • #538
Re: [v2] ice: Fix freeing uninitialized pointers
Sun, 24 Mar 2024 14:22:31 +0100
Markus Elfring <[email protected]> • #537
Re: [PATCH v2 net] ice: Fix freeing uninitialized pointers
Sun, 24 Mar 2024 13:43:12 +0300
Dan Carpenter <[email protected]> • #536
Re: [PATCH v2 net] ice: Fix freeing uninitialized pointers
Sat, 23 Mar 2024 17:56:29 +0100
Markus Elfring <[email protected]> • #535
Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Fri, 22 Mar 2024 10:55:28 +0300
Dan Carpenter <[email protected]> • #534
Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Fri, 22 Mar 2024 10:49:26 +0300
Dan Carpenter <[email protected]> • #533
Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Fri, 22 Mar 2024 15:05:10 +0800 (GMT+08:00)
李书畅 <[email protected]> • #532
Re: [PATCH] kernel_user_data: add ceph_decode_n() as returning user data
Wed, 20 Mar 2024 14:45:52 +0300
Dan Carpenter <[email protected]> • #531
[PATCH] kernel_user_data: add ceph_decode_n() as returning user data
Wed, 20 Mar 2024 03:07:38 -0700
Harshit Mogalapalli <[email protected]> • #530
Improving data processing with prepared SQL statements
Mon, 18 Mar 2024 15:56:57 +0100
Markus Elfring <[email protected]> • #529
Growing development interests for Smatch issues?
Mon, 18 Mar 2024 12:30:26 +0100
Markus Elfring <[email protected]> • #528
Growing benefits from the Smatch cross function database?
Sun, 17 Mar 2024 10:33:29 +0100
Markus Elfring <[email protected]> • #527
Re: smatch and locking checks
Fri, 15 Mar 2024 13:56:08 +0300
Dan Carpenter <[email protected]> • #526
Re: smatch and locking checks
Fri, 15 Mar 2024 13:46:29 +0300
Dan Carpenter <[email protected]> • #525
Re: smatch and locking checks
Fri, 15 Mar 2024 13:35:24 +0300
Dan Carpenter <[email protected]> • #524
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 11:37:54 +0300
Dan Carpenter <[email protected]> • #523
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 16:29:25 +0800 (GMT+08:00)
李书畅 <[email protected]> • #522
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 11:08:37 +0300
Dan Carpenter <[email protected]> • #521
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 15:51:37 +0800 (GMT+08:00)
李书畅 <[email protected]> • #520
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 10:29:01 +0300
Dan Carpenter <[email protected]> • #519
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 14:29:13 +0800 (GMT+08:00)
李书畅 <[email protected]> • #518
Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Wed, 13 Mar 2024 08:58:11 +0300
Dan Carpenter <[email protected]> • #517
Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Tue, 12 Mar 2024 22:22:06 +0800 (GMT+08:00)
李书畅 <[email protected]> • #516
Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Tue, 12 Mar 2024 20:38:43 +0800 (GMT+08:00)
李书畅 <[email protected]> • #515
Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 21:23:35 +0800 (GMT+08:00)
李书畅 <[email protected]> • #514
Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 15:54:30 +0800 (GMT+08:00)
李书畅 <[email protected]> • #513
Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 10:39:08 +0300
Dan Carpenter <[email protected]> • #512
Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 10:33:24 +0300
Dan Carpenter <[email protected]> • #511
Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 15:07:40 +0800 (GMT+08:00)
李书畅 <[email protected]> • #510
Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 13:31:35 +0800 (GMT+08:00)
李书畅 <[email protected]> • #509
Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 08:01:54 +0300
Dan Carpenter <[email protected]> • #508
Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Mon, 11 Mar 2024 08:00:42 +0300
Dan Carpenter <[email protected]> • #507
Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
Sun, 10 Mar 2024 13:39:41 +0800 (GMT+08:00)
李书畅 <[email protected]> • #506
Re: Re: Re: Re: Re: about using smatch in all debian C code
Sun, 10 Mar 2024 12:56:47 +0800 (GMT+08:00)
李书畅 <[email protected]> • #505
Re: Re: Re: Re: Re: about using smatch in all debian C code
Thu, 7 Mar 2024 18:27:29 +0800 (GMT+08:00)
李书畅 <[email protected]> • #504
Re: Re: Re: Re: about using smatch in all debian C code
Thu, 7 Mar 2024 12:49:00 +0300
Dan Carpenter <[email protected]> • #503
Re: Re: Re: Re: about using smatch in all debian C code
Thu, 7 Mar 2024 11:43:15 +0800 (GMT+08:00)
李书畅 <[email protected]> • #502
Re: Re: Re: about using smatch in all debian C code
Wed, 6 Mar 2024 22:25:40 +0300
Dan Carpenter <[email protected]> • #501
Re: Re: Re: about using smatch in all debian C code
Wed, 6 Mar 2024 21:40:14 +0300
Dan Carpenter <[email protected]> • #500
Re: Re: Re: about using smatch in all debian C code
Wed, 6 Mar 2024 17:47:30 +0800 (GMT+08:00)
李书畅 <[email protected]> • #499
Re: Re: about using smatch in all debian C code
Wed, 6 Mar 2024 09:40:12 +0300
Dan Carpenter <[email protected]> • #498
Re: Re: about using smatch in all debian C code
Wed, 6 Mar 2024 14:12:45 +0800 (GMT+08:00)
李书畅 <[email protected]> • #497
Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
Wed, 21 Feb 2024 19:02:49 -0500
Kent Overstreet <[email protected]> • #496
Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
Wed, 21 Feb 2024 09:01:26 +0300
Dan Carpenter <[email protected]> • #495
Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
Tue, 20 Feb 2024 16:26:38 -0500
Kent Overstreet <[email protected]> • #494
Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
Tue, 20 Feb 2024 14:39:35 +0300
Dan Carpenter <[email protected]> • #493
Re: [PATCH] untracked_param: fix compilation errors with GCC 14
Mon, 22 Jan 2024 09:25:19 +0300
Dan Carpenter <[email protected]> • #492
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.