Semantic Matching Tool

• Thread Index

• Re: Smatch - possible regression in unreachable code check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch - possible regression in unreachable code check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Smatch - possible regression in unreachable code check
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: check locking re-write
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 2/2] smatch: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• Re: check locking re-write
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH 2/2] smatch: fix typos
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 0/2] Fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• [PATCH 2/2] smatch: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• [PATCH 1/2] smatch: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• Re: [PATCH 1/2] doc: fix typos
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 2/2] scripts: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• [PATCH 1/2] doc: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• Re: smatch regression - after recent update
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: smatch regression - after recent update
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• smatch regression - after recent update
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• check locking re-write
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Question on a error handling related warning
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Question on a error handling related warning
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: Bug-report: Smatch treats scoped_guard() as unreachable code ?
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: Bug-report: Smatch treats scoped_guard() as unreachable code ?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Bug-report: Smatch treats scoped_guard() as unreachable code ?
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: FP with unreachable code check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: False positive due to MACROs in nfsd code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: min/max() changes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• FP with unreachable code check
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: min/max() changes
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: min/max() changes
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• False positive due to MACROs in nfsd code
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: min/max() changes
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: min/max() changes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: min/max() changes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: min/max() changes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• min/max() changes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Treat macro call like ordinary functions in smatch.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Treat macro call like ordinary functions in smatch.
  • From: Hongyi Lu <jwnhy0@xxxxxxxxx>
• Re: Treat macro call like ordinary functions in smatch.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Treat macro call like ordinary functions in smatch.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Treat macro call like ordinary functions in smatch.
  • From: Hongyi Lu <jwnhy0@xxxxxxxxx>
• Re: Treat macro call like ordinary functions in smatch.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 0/2] Support custom build directory for kernel
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 1/2] kchecker: Fix --outfile handling
  • From: Cristian Ciocaltea <cristian.ciocaltea@xxxxxxxxxxxxx>
• [PATCH 2/2] kernel: Add support for custom build directory
  • From: Cristian Ciocaltea <cristian.ciocaltea@xxxxxxxxxxxxx>
• [PATCH 0/2] Support custom build directory for kernel
  • From: Cristian Ciocaltea <cristian.ciocaltea@xxxxxxxxxxxxx>
• Re: [PATCH] sentinel_ctltable: Add a check for sentinel elements in ctl_table arrays
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] sentinel_ctltable: Add a check for sentinel elements in ctl_table arrays
  • From: Joel Granados via B4 Relay <devnull+j.granados.samsung.com@xxxxxxxxxx>
• Re: How do I make a contribution to the automatic analysis done on the kernel
  • From: Joel Granados <j.granados@xxxxxxxxxxx>
• Re: How do I make a contribution to the automatic analysis done on the kernel
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• How do I make a contribution to the automatic analysis done on the kernel
  • From: Joel Granados <j.granados@xxxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: likely/unlikely usage validation
  • From: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx>
• likely/unlikely usage validation
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: [PATCH] pre-proc: use uname() syscall instead of invoking uname
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] pre-proc: use uname() syscall instead of invoking uname
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] pre-proc: use uname() syscall instead of invoking uname
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: About building the database for smatch
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• About building the database for smatch
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: [PATCH 0/3] Documentation/smatch: RST conversion and fixes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 3/3] Documentation/smatch: fix typo in submitting-patches.md
  • From: Javier Carrasco <javier.carrasco.cruz@xxxxxxxxx>
• [PATCH 2/3] Documentation/smatch: convert to RST
  • From: Javier Carrasco <javier.carrasco.cruz@xxxxxxxxx>
• [PATCH 1/3] Documentation/smatch: fix paths in the examples
  • From: Javier Carrasco <javier.carrasco.cruz@xxxxxxxxx>
• [PATCH 0/3] Documentation/smatch: RST conversion and fixes
  • From: Javier Carrasco <javier.carrasco.cruz@xxxxxxxxx>
• Re: [v2] ice: Fix freeing uninitialized pointers
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Re: [PATCH v2 net] ice: Fix freeing uninitialized pointers
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH v2 net] ice: Fix freeing uninitialized pointers
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: [PATCH] kernel_user_data: add ceph_decode_n() as returning user data
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] kernel_user_data: add ceph_decode_n() as returning user data
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Improving data processing with prepared SQL statements
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Growing development interests for Smatch issues?
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Growing benefits from the Smatch cross function database?
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Re: smatch and locking checks
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch and locking checks
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch and locking checks
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [bug report] bcachefs: missing error checks for bio_alloc_bioset()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] untracked_param: fix compilation errors with GCC 14
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] untracked_param: fix compilation errors with GCC 14
  • From: Lukáš Zaoral <lzaoral@xxxxxxxxxx>
• PSA: this list has moved to new vger infra (no action required)
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH smatch] check_uninitialized_kobj: Add a new check
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH smatch] check_uninitialized_kobj: Add a new check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH smatch] check_uninitialized_kobj: Add a new check
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: sparse feature request: nocast integer types
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: sparse feature request: nocast integer types
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: sparse feature request: nocast integer types
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• PSA: smatch is now archived on lore.kernel.org
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: about using smatch in all debian C code
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• about using smatch in all debian C code(the previous email forgot to cc Dan，please ignore it)
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• about using smatch in all debian C code
  • From: 李书畅 <lishuchang@xxxxxxxxxxx>
• Re: Kernel config usage
  • From: Umang Jain <umang.jain@xxxxxxxxxxxxxxxx>
• Re: Kernel config usage
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Kernel config usage
  • From: Umang Jain <umang.jain@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2] check_unwind: Add request/release_firmware to the function table
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH v2] check_unwind: Add request/release_firmware to the function table
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH] check_unwind: Add request/release_firmware to the function table
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH] check_unwind: Add request/release_firmware to the function table
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_unwind: Add request/release_firmware to the function table
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: Need help with understanding format in check_unwind.c
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Need help with understanding format in check_unwind.c
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: Need help with understanding format in check_unwind.c
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Need help with understanding format in check_unwind.c
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH] check_ida_alloc: Improve check to not warn when min is '1'
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_ida_alloc: Improve check to not warn when min is '1'
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: List some ideas about Smatch as public projects in our open source club
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: List some ideas about Smatch as public projects in our open source club
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: List some ideas about Smatch as public projects in our open source club
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: The errors I encountered when Smatch builds the latest mainline
  • From: 慕冬亮 <dzm91@xxxxxxxxxxx>
• Re: The errors I encountered when Smatch builds the latest mainline
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 0/5] accel/qaic: Improve bounds checking in encode/decode
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: The errors I encountered when Smatch builds the latest mainline
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: The errors I encountered when Smatch builds the latest mainline
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• The errors I encountered when Smatch builds the latest mainline
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: [PATCH] spi: spi-geni-qcom: correctly handle -EPROBE_DEFER from dma_request_chan()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] spi: spi-geni-qcom: correctly handle -EPROBE_DEFER from dma_request_chan()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Binaries in source tree
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Binaries in source tree
  • From: Benson Muite <benson_muite@xxxxxxxxxxxxx>
• Re: Binaries in source tree
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Binaries in source tree
  • From: Benson Muite <benson_muite@xxxxxxxxxxxxx>
• Binaries in source tree
  • From: Benson Muite <benson_muite@xxxxxxxxxxxxx>
• Re: devm_ on lists
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: devm_ on lists
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: devm_ on lists
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: devm_ on lists
  • From: Marion & Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• devm_ on lists
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: How to interpret this warning.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Question about a smatch warning.
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH RFC net] tipic: guard against buffer overrun in bearer_name_validate()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Questions about the checker replacing divide condition with a compare condition
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Questions about the checker replacing divide condition with a compare condition
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: [PATCH] Input: xpad - fix GPF in xpad_probe
  • From: Dongliang Mu <dzm91@xxxxxxxxxxx>
• Re: [PATCH] Input: xpad - fix GPF in xpad_probe
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: How does paired function checking implement in Smatch?
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: How does paired function checking implement in Smatch?
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: How does paired function checking implement in Smatch?
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: How does paired function checking implement in Smatch?
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: How does paired function checking implement in Smatch?
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH linux_next v2] iio: adc: ti-ads1100: fix passing a valid pointer to 'PTR_ERR'
  • From: Dan Carpenter <error27@xxxxxxxxx>
• How does paired function checking implement in Smatch?
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: [PATCH] atm: he: fix potential ioremap leak of membase in he_dev
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: Who is looking at CVEs to prevent them?
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: Who is looking at CVEs to prevent them?
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: new check for missing error codes
  • From: Marion JAILLET <marion.jaillet@xxxxxxxxxx>
• New checks for NULL and uninitalized parameters
  • From: Dan Carpenter <error27@xxxxxxxxx>
• new check for missing error codes
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH v2] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH] direct_return_instead_of_goto: Delete duplicate conditions
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Dan Carpenter <error27@xxxxxxxxx>
• [PATCH v2] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Marion & Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: [PATCH] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Marion JAILLET <marion.jaillet@xxxxxxxxxx>
• [PATCH] direct_return_instead_of_goto: Delete duplicate conditions
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• [PATCH] direct_return_instead_of_goto: don't warn about other forms of printks
  • From: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx>
• Re: Smatch or Coccinelle for BPF static code analysis
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Smatch or Coccinelle for BPF static code analysis
  • From: "Laurent Philippart (Nokia)" <laurent.philippart@xxxxxxxxx>
• Re: hugetlb BUILD REGRESSION in linux-next20221121
  • From: Sidhartha Kumar <sidhartha.kumar@xxxxxxxxxx>
• Re: hugetlb BUILD REGRESSION in linux-next20221121
  • From: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx>
• Re: hugetlb BUILD REGRESSION in linux-next20221121
  • From: Dan Carpenter <error27@xxxxxxxxx>
• hugetlb BUILD REGRESSION in linux-next20221121
  • From: Sidhartha Kumar <sidhartha.kumar@xxxxxxxxxx>
• DB changes and job changes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 2/2] check_host_input: add a new pattern
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• [PATCH 1/2] host_data: export checking for host function name/param
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• Re: [PATCH] allocation: Track the size of allocated elements
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] allocation: Track the size of allocated elements
  • From: Marion & Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] allocation: Track the size of allocated elements
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] allocation: Track the size of allocated elements
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] allocation: Add some kv... variants
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] continue_vs_break: Fix some style issue
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH 1/2] smatch_allocations: Record the function that allocates memory
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 2/2] check_freeing_devm: Take advantage of the new add_allocation hook.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 2/2] check_freeing_devm: Take advantage of the new add_allocation hook.
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH 1/2] smatch_allocations: Record the function that allocates memory
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] smatch_allocations: Add devm_kmemdup() to list
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] smatch_allocations: Remove dma_alloc_consistent() from the list
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] smatch_allocations: Give a hint about dma_alloc_(attrs|coherent)
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] smatch_allocations: Fix and improve the kernel_alloc_funcs list
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] smatch_allocations: Remove dma_alloc_consistent() from the list
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] smatch_allocations: Give a hint about dma_alloc_(attrs|coherent)
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Smatch v1.73 released
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• RE: [PATCH] smatch_kernel_host_data: enable additional debug
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: [PATCH] smatch_kernel_host_data: enable additional debug
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_ida_alloc: Add a new check to spot invalid conversion from ida_simple_get()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_ida_alloc: Add a new check to spot invalid conversion from ida_simple_get()
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] check_dma_mapping_error: Remove check for pci_dma_mapping_error()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_dma_mapping_error: Remove check for pci_dma_mapping_error()
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] check_release_resource: Remove some test about functions that are no more part of linux
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_checking_for_null_instead_of_err_ptr: Save a few cycles
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] check_release_resource: Remove some test about functions that are no more part of linux
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• new locking check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_freeing_devm: Report the correct function name that triggered the warning
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] Remove pci_alloc_consistent() and pci_alloc_coherent() checks
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] Remove pci_alloc_consistent() and pci_alloc_coherent() checks
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_all_func_returns: Fix a test against "vfprintf"
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_freeing_devm: Add some new devm_ function
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Marion & Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] check_release_resource: Use INT_PTR instead of hand writing it
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_all_func_returns: Fix a test against "vfprintf"
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] check_freeing_devm: Add some new devm_ function
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] check_freeing_devm: Report the correct function name that triggered the warning
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] check_release_resource: Use INT_PTR instead of hand writing it
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] check_bogus_irqrestore: Preparation work in order to add more functions
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] check_kvmalloc_NOFS: Report the correct function name that triggered the warning
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH] kmalloc_wrong_size: Preparation work in order to add more functions
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] test_bit: Add some more functions to test.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] kmalloc_wrong_size: Preparation work in order to add more functions
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] test_bit: Add some more functions to test.
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• [PATCH] test_bit: Report the correct function name that triggered the warning
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• RE: [PATCH] smatch_kernel_host_data: enable additional debug
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: [PATCH] smatch_kernel_host_data: enable additional debug
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] smatch_kernel_host_data: enable additional debug
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• RE: [PATCH] check_spectre: Add a switch to optionally use host data
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: [PATCH] check_spectre: Add a switch to optionally use host data
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• RE: [PATCH] check_spectre: Add a switch to optionally use host data
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: [PATCH] check_spectre: Add a switch to optionally use host data
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_spectre: Add a switch to optionally use host data
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• [PATCH] Add tracking of host/VMM data for confidential computing
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• Re: [PATCH v3 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v3 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: David Gow <davidgow@xxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: David Gow <davidgow@xxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: David Gow <davidgow@xxxxxxxxxx>
• Re: [PATCH v3 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH v3 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: [PATCH v3 0/2] Add a section for static analysis tools
  • From: David Gow <davidgow@xxxxxxxxxx>
• [PATCH v3 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• [PATCH v3 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• [PATCH v3 0/2] Add a section for static analysis tools
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [PATCH v2 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: David Gow <davidgow@xxxxxxxxxx>
• Re: [PATCH v2 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: David Gow <davidgow@xxxxxxxxxx>
• Re: [PATCH v2 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Daniel Latypov <dlatypov@xxxxxxxxxx>
• [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• [PATCH v2 1/2] Documentation: dev-tools: Add a section for static analysis tools
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• [PATCH v2 0/2] Add a section for static analysis tools
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• Re: [cocci] [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [cocci] [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: David Gow <davidgow@xxxxxxxxxx>
• Re: [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Daniel Latypov <dlatypov@xxxxxxxxxx>
• Re: [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• [PATCH] Documentation: dev-tools: Add a section for static analysis tools
  • From: Marcelo Schmitt <marcelo.schmitt1@xxxxxxxxx>
• Re: alloc_page leaks tracing
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: alloc_page leaks tracing
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: alloc_page leaks tracing
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] media: lirc: suppress false positive smatch warning
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] media: lirc: suppress false positive smatch warning
  • From: Sean Young <sean@xxxxxxxx>
• [PATCH] media: lirc: suppress false positive smatch warning
  • From: Sean Young <sean@xxxxxxxx>
• Re: alloc_page leaks tracing
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• alloc_page leaks tracing
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: [PATCH] Quick trial on tracing host inputs
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] Quick trial on tracing host inputs
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] Quick trial on tracing host inputs
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• RE: [PATCH 1/1] check_host_input: add a pattern
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: [PATCH 1/1] check_host_input: add a pattern
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] Quick trial on tracing host inputs
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• [PATCH 1/1] check_host_input: add a pattern
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• [PATCH 0/1] New smatch pattern for Confidential Cloud Computing
  • From: Elena Reshetova <elena.reshetova@xxxxxxxxx>
• Re: FW: [error27/smatch] smatch misidentifies uninitialized variable after switch with no default: (Issue #3)
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• FW: [error27/smatch] smatch misidentifies uninitialized variable after switch with no default: (Issue #3)
  • From: "Brandeburg, Jesse" <jesse.brandeburg@xxxxxxxxx>
• Re: [PATCH v1 1/3] media: staging: tegra-vde: Support reference picture marking
  • From: Dmitry Osipenko <digetx@xxxxxxxxx>
• Re: [PATCH v1 1/3] media: staging: tegra-vde: Support reference picture marking
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• offline for the next two weeks
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• RE: BKM on generating a call graph for smatch warnings
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: BKM on generating a call graph for smatch warnings
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Smatch v1.72 released
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• BKM on generating a call graph for smatch warnings
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• Re: [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_netdev_priv: warn about using netdev priv data after free_netdev
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• Re: [PATCH] check_do_while_loop_limit: implements checker for do_while loops
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_do_while_loop_limit: implements checker for do_while loops
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH] check_do_while_loop_limit: implements checker for do_while loops
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] check_do_while_loop_limit: implements checker for do_while loops
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] bits_clear and bits_set: Track bits cleared and set inside a function
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] extra: Fix handle_bit_test so that null set condition is taken care of
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] check_iterator: Warn about end of loop tests for list_for_each_entry
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] power_of_two: Track variables which are powers of two
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH 2/2] extra: Fix handle_bit_test so that null set condition is taken care of
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH 2/2] extra: Fix handle_bit_test so that null set condition is taken care of
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 2/2] extra: Fix handle_bit_test so that null set condition is taken care of
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH 1/2] extra: Fix false output of handle_AND_op and handle_AND_condition
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH 2/2] [PATCH 2/2] Fix handle_bit_test so that null set condition is taken care of
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 1/2] extra: Fix false output of handle_AND_op and handle_AND_condition
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 2/2] Fix handle_bit_test so that null set condition is taken care of
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 2/2] [PATCH 2/2] Fix handle_bit_test so that null set condition is taken care of
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH 1/2] extra: Fix false output of handle_AND_op and handle_AND_condition
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH 1/2] extra: Fix false output of handle_AND_op and handle_AND_condition
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 2/2] Fix handle_bit_test so that null set condition is taken care of
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH 1/2] extra: Fix false output of handle_AND_op and handle_AND_condition
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: [PATCH] extra: Fixed false output of handle_AND_op and handle_AND_condition
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] extra: Fixed handle_bit_test so that null set condition is taken care of
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] extra: Fixed handle_bit_test so that null set condition is taken care of
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] extra: Fixed handle_bit_test so that null set condition is taken care of
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• [PATCH] extra: Fixed false output of handle_AND_op and handle_AND_condition
  • From: Harshvardhan Jha <harshvardhan.jha@xxxxxxxxxx>
• Re: Retrieving status of local variables
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Retrieving status of local variables
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Retrieving status of local variables
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Retrieving status of local variables
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• RE: Smatch mailing list archives
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: Smatch mailing list archives
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch mailing list archives
  • From: Oleg Drokin <green@xxxxxxxxxxxxx>
• RE: Smatch mailing list archives
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• RE: Smatch mailing list archives
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: Smatch mailing list archives
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch mailing list archives
  • From: Oleg Drokin <green@xxxxxxxxxxxxx>
• RE: Smatch mailing list archives
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• Re: Smatch mailing list archives
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Smatch mailing list archives
  • From: "Reshetova, Elena" <elena.reshetova@xxxxxxxxx>
• possible incompletely defined array smatch test addition?
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: compiling smatch 1.71
  • From: Fabio Aiuto <fabioaiuto83@xxxxxxxxx>
• Re: compiling smatch 1.71
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• compiling smatch 1.71
  • From: Fabio Aiuto <fabioaiuto83@xxxxxxxxx>
• Re: smatch and copy_{to,from}_user return values
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch and copy_{to,from}_user return values
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch and copy_{to,from}_user return values
  • From: Heiko Carstens <hca@xxxxxxxxxxxxx>
• Re: smatch and copy_{to,from}_user return values
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• smatch and copy_{to,from}_user return values
  • From: Rasmus Villemoes <rasmus.villemoes@xxxxxxxxx>
• Re: False Positive return_cast check
  • From: Benjamin Block <bblock@xxxxxxxxxxxxx>
• Re: False Positive return_cast check
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• False Positive return_cast check
  • From: Benjamin Block <bblock@xxxxxxxxxxxxx>
• smatch v1.71 released
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch v1.71 released
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• smatch v1.71 released
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan McDonald <danmcd@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan McDonald <danmcd@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan McDonald <danmcd@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Intel i40e code finds smatch bug
  • From: Dan McDonald <danmcd@xxxxxxxxxx>
• Intel i40e code finds smatch bug
  • From: Dan McDonald <danmcd@xxxxxxxxxx>
• Re: [PATCH] Makefile: Install database in a share directory
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] Makefile: Install database in a share directory
  • From: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
• Re: [PATCH] Set __STDC_VERSION__ for std89
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• [PATCH] Set __STDC_VERSION__ for std89
  • From: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
• Re: [PATCH] Makefile: Install database in a share directory
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] Makefile: Install database in a share directory
  • From: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
• Re: [PATCH] Check for NULL stmt in check_all_func_returns
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] Check for NULL stmt in check_all_func_returns
  • From: john.levon@xxxxxxxxxx
• current HEAD build broken
  • From: John Levon <john.levon@xxxxxxxxxx>
• Re: smatch: misreported 'mask and shift to zero'
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Misleading messages from match 0.6.1-rc1
  • From: Toomas Soome <tsoome@xxxxxx>
• Re: Misleading messages from match 0.6.1-rc1
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• smatch: misreported 'mask and shift to zero'
  • From: Toomas Soome <tsoome@xxxxxx>
• Misleading messages from match 0.6.1-rc1
  • From: Toomas Soome <tsoome@xxxxxx>
• [PATCH 7/8] correct sparcv9 defines
  • From: john.levon@xxxxxxxxxx
• [PATCH 8/8] predefine "i386" if needed
  • From: john.levon@xxxxxxxxxx
• [PATCH 6/8] pre-define __unix__ and friends
  • From: john.levon@xxxxxxxxxx
• [PATCH 5/8] add necessary defined for sunos-derived systems
  • From: john.levon@xxxxxxxxxx
• [PATCH 4/8] define __PRAGMA_REDEFINE_EXTNAME
  • From: john.levon@xxxxxxxxxx
• [PATCH 3/8] add predefine_nostd()
  • From: john.levon@xxxxxxxxxx
• [PATCH 2/8] alt definition for STANDARD_GNU89 & friends
  • From: john.levon@xxxxxxxxxx
• [PATCH 1/8] allow to test the standard version outside of lib.c
  • From: john.levon@xxxxxxxxxx
• Patch series: pre-defines update
  • From: john.levon@xxxxxxxxxx
• Re: [PATCH] arch: add missing predefines: __amd64 & __amd64__
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] arch: add missing predefines: __amd64 & __amd64__
  • From: John Levon <john.levon@xxxxxxxxxx>
• Re: [PATCH] arch: add missing predefines: __amd64 & __amd64__
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] arch: add missing predefines: __amd64 & __amd64__
  • From: john.levon@xxxxxxxxxx
• [PATCH] disable warning about long double in unions
  • From: john.levon@xxxxxxxxxx
• [PATCH 1/2] Correct FP minimum handling
  • From: john.levon@xxxxxxxxxx
• Re: [PATCH] Use sm_debug for a debug message
  • From: John Levon <john.levon@xxxxxxxxxx>
• Re: sval_type_max() sadness
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• sval_type_max() sadness
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: [RFC PATCH 5/7] kernel_user_data: track parameter __untagged annotations
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [PATCH] function attributes apply to the function declaration
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: [PATCH] function attributes apply to the function declaration
  • From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] function attributes apply to the function declaration
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: check_signed.c false negative
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: check_signed.c false negative
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] Add -Wexternal-function-has-definition
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Remove bogus option from sparse manual.
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Fix divide by zero message
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Add check_all_func_returns
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] unreachable code should use sm_warning()
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Fix unused variable in macro_table.c
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Implement memory tracker for Solarish systems
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Set smatch to output to stdout
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Remove unused variable from check_memset.c
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Clean up unused -W options
  • From: John Levon <john.levon@xxxxxxxxxx>
• [PATCH] Add check_cmn_err
  • From: John Levon <john.levon@xxxxxxxxxx>
• check_signed.c false negative
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] Tagged Pointer Detection
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH 5/7] kernel_user_data: track parameter __untagged annotations
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [RFC PATCH 5/7] kernel_user_data: track parameter __untagged annotations
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [RFC PATCH 5/7] kernel_user_data: track parameter __untagged annotations
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [RFC PATCH 4/7] smdb.py: add find_tagged and parse_warns_tagged commands
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 7/7] Documentation: add guide for tagged addresses
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 6/7] smdb.py: filter out __untagged from find_tagged results
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 5/7] kernel_user_data: track parameter __untagged annotations
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 4/7] smdb.py: add find_tagged and parse_warns_tagged commands
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 3/7] arm64: add check for comparison against tagged address
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 2/7] smdb.py: remove undocumented test command
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 1/7] build: Add '-lm' build flag
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [RFC PATCH 0/7] Tagged Pointer Detection
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [PATCH 0/4] Miscellaneous fixes
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: noreturn attribute doesn't work in smatch
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: noreturn attribute doesn't work in smatch
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: noreturn attribute doesn't work in smatch
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: noreturn attribute doesn't work in smatch
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: noreturn attribute doesn't work in smatch
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• noreturn attribute doesn't work in smatch
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: Packed struct size issue
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Packed struct size issue
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Packed struct size issue
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] Miscellaneous fixes
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Address space of struct member
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Differing range values for same callsite/param
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [PATCH 4/4] kchecker: remove debug
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [PATCH 3/4] user_data: Recognize uaccess for non-x86 architectures
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [PATCH 2/4] smdb.py: fix param tracking now that we use $ instead of p
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [PATCH 1/4] smdb.py: fix handling of capped ranges
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• [PATCH 0/4] Miscellaneous fixes
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Differing range values for same callsite/param
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [RFC] arm64: Detecting tagged addresses
  • From: Vincenzo Frascino <vincenzo.frascino@xxxxxxx>
• Re: [PATCH] kernel: Add support for cross-build kernels
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] kernel: Add support for cross-build kernels
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [PATCH] db/smdb: add info command with type filtering
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: [PATCH] db/smdb: add info command with type filtering
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] db/smdb: add info command with type filtering
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Detecting user data on base types
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Detecting user data on base types
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Smatch context checking feature ?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Smatch context checking feature ?
  • From: Himanshu Jha <himanshujha199640@xxxxxxxxx>
• Re: Detecting user data on base types
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• Re: Detecting user data on base types
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Detecting user data on base types
  • From: Andrew Murray <andrew.murray@xxxxxxx>
• passing zero to PTR_ERR() warnings
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [kernel-build 2/2] kernel: forward build failures
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: [kernel-build 2/2] kernel: forward build failures
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [kernel-build 2/2] kernel: forward build failures
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [kernel-build 1/2] kernel: modify build via env
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: I would like to contribute to smatch
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• I would like to contribute to smatch
  • From: Joel Savitz <jsavitz@xxxxxxxxxx>
• Re: Odd smatch issue?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Odd smatch issue?
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: Odd smatch issue?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Odd smatch issue?
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: Odd smatch issue?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Odd smatch issue?
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH] Remove -Wempty-character-constant
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: Sync smatch with sparse?
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Sync smatch with sparse?
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• [PATCH] Look across the entire compile line for smatch arguments
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 12/12] Add check_all_func_returns
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 11/12] Add illumos projects
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 10/12] Track sparse-level warnings and errors too, and respect them in smatch's exit code.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 09/12] Convert some sm_msg() into more specific reporting routines.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 08/12] Convert sm_msg() with an error: prefix into sm_error()
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 07/12] Convert all sm_msg("warn:.." into sm_warning()
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 06/12] Regularise error reporting
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 05/12] Look across the entire compile line for smatch arguments
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 04/12] sparse: add -Wempty-character-constant
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 03/12] sparse: add -Wbig-constants
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 02/12] sparse: add -Wno-non-ansi-function-declaration
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 01/12] sparse: correctly handle "-D foo" and "-U foo"
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] Introduce skipped_functions
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• [PATCH 12/18] Add progname to sm_prefix()
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 13/18] sparse: prefix output with progname
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 04/18] Fix escape_newlines: we were not NIL-terminating the string properly, and were also mis-counting the loop indices.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 14/18] Track sparse-level warnings and errors too, and respect them in smatch's exit code.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 07/18] sparse: add -Wbig-constants
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 02/18] sparse: define __x86_64; some software checks for this not __x86_64__
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 01/18] Allow additional CFLAGS to be specified, e.g. "CFLAGS=-m64 make"
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 11/18] Convert some sm_msg() into more specific reporting routines.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 18/18] sparse: add -Wempty-character-constant
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 09/18] Convert all sm_msg("warn:.." into sm_warning()
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 08/18] Start to regularise error reporting. The idea is that parse errors and other internal errors are reported back in the exit code, while still reporting the context where needed.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 17/18] don't try to parse silenced functions
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 03/18] sparse: lib.c should handle being built 32-bit, compiling 64-bit, on x86.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 16/18] Look across the entire compile line for smatch arguments. This makes smatch arguments much easier to provide in Makefiles, and sparse itself doesn't overlap.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 10/18] Convert sm_msg() with an error: prefix into sm_error()
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 06/18] sparse: add -Wno-non-ansi-function-declaration
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• [PATCH 15/18] Add illumos projects. Add a new check type that looks for unchecked returns on *all* functions, mimicking the old behaviour of lint.
  • From: John Levon <levon@xxxxxxxxxxxxxxxxx>
• Re: [xen 1/6] math: increase bounds and buffers
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [xen 1/6] math: increase bounds and buffers
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Smatch for Xen
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [xen 5/6] user_data: add register read function
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [xen 4/6] user_data: match Xen copy_from_guest
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: [xen 5/6] user_data: add register read function
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: [xen 4/6] user_data: match Xen copy_from_guest
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [xen 5/6] user_data: add register read function
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [xen 1/6] math: increase bounds and buffers
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [xen 3/6] user_data: match some Xen hypercalls
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [xen 2/6] user_data: add ends_with method
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [xen 4/6] user_data: match Xen copy_from_guest
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [xen 5/6] user_data: add register read function
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [xen 6/6] user_data: add hypercall sub calls
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [xen 1/6] math: increase bounds and buffers
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Smatch for Xen
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch validation tests fail
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• smatch validation tests fail
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• [PATCH 3/3] add support for mode __byte__
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• [PATCH 2/3] add support for mode __pointer__
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• [PATCH 1/3] mode keywords don't need MOD_{CHAR,LONG,...}
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• [PATCH 0/3] add support for mode __pointer__ & __byte__
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Smatch for Xen
  • From: Norbert Manthey <nmanthey@xxxxxxxxx>
• Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address sanitizer
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address sanitizer
  • From: Andrey Konovalov <andreyknvl@xxxxxxxxxx>
• Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address sanitizer
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: uninitialized symbol 'xxxx' is too overzealous?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: uninitialized symbol 'xxxx' is too overzealous?
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: uninitialized symbol 'xxxx' is too overzealous?
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: uninitialized symbol 'xxxx' is too overzealous?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: uninitialized symbol 'xxxx' is too overzealous?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• uninitialized symbol 'xxxx' is too overzealous?
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: Checking analysis dependencies for “smatch”
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Checking analysis dependencies for “smatch”
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: tracing back a variable
  • From: "Gustavo A. R. Silva" <gustavo@xxxxxxxxxxxxxx>
• Re: tracing back a variable
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• tracing back a variable
  • From: "Gustavo A. R. Silva" <gustavo@xxxxxxxxxxxxxx>
• Checking analysis dependencies for “smatch”
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Checking further software evolution around “Smatch”
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Using smatch with meson
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Using smatch with meson
  • From: "Thomas H.P. Andersen" <phomes@xxxxxxxxx>
• Re: [PATCH 2/3] smatch_type.c: comparison expressions always have type int
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 3/3] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 3/3] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] smatch_type.c: comparison expressions always have type int
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] smatch_type.c: fix type of pointer diff
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 0/3] type fixes, printf warning
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 5/5] check_kernel_printf.c: warn about "%lx", (long)ptr
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 4/5] check_kernel_printf.c: prepare for more tests for integer specifiers
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 3/5] check_kernel_printf.c: check %pOF argument is struct device_node*
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/5] check_kernel_printf.c: remove copy-pastoed variable
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/5] check_kernel_printf.c: use get_real_base_type in typedef_lookup
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 0/5] check_kernel_printf stuff
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Andrew Zhu Aday <andrew.aday@xxxxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Andrew Zhu Aday <andrew.aday@xxxxxxxxxxxx>
• Re: Tracking Implicit Dependencies
  • From: Andrew Zhu Aday <andrew.aday@xxxxxxxxxxxx>
• Tracking Implicit Dependencies
  • From: Andrew Zhu Aday <andrew.aday@xxxxxxxxxxxx>
• Re: SMATCH indicates warning to almost all files in Linux Kernel + ARM
  • From: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx>
• Re: SMATCH indicates warning to almost all files in Linux Kernel + ARM
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: SMATCH indicates warning to almost all files in Linux Kernel + ARM
  • From: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx>
• Re: SMATCH indicates warning to almost all files in Linux Kernel + ARM
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Hangs while building the cross function DB
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Can smatch detect this bug?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: sparse on scripts/kconfig/*.c
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: sparse on scripts/kconfig/*.c
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Fwd: [PATCH] Makefile: remove SMATCH_DATA smatch_data/kernel.balanced_funcs item
  • From: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
• Re: sparse on scripts/kconfig/*.c
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: sparse on scripts/kconfig/*.c
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: sparse on scripts/kconfig/*.c
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• C Safety and Security Study Group
  • From: Laurence Urhegyi <laurence.urhegyi@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] check_kernel_printf: check that %pg gets a block_device
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 1/3] check_kernel_printf: check that %pg gets a block_device
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 3/3] check_kernel_printf.c: handle new definition of KERN_CONT
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] check_kernel_printf.c: %pj ended up being %pG
  • From: Rasmus Villemoes <rv@xxxxxxxxxxxxxxxxxx>
• Re: smatch db errors?
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: smatch db errors?
  • From: Silvan Jegen <s.jegen@xxxxxxxxx>
• smatch db errors?
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: [PATCH] slist: Properly handle one-way merges
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: [PATCH] slist: Properly handle one-way merges
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] slist: Properly handle one-way merges
  • From: Oleg Drokin <green@xxxxxxxxxxxxxx>
• Re: [PATCH] slist: Properly handle one-way merges
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>