Julia Lawall
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Julia Lawall has a total of 48 co-authors. Here are the top co-authors by number of shared publications:
- David Lo
School of Computing and Information Systems, Singapore Management University, Singapore, Singapore
8 shared publications - Stefanus Agus Haryono
School of Information Systems Singapore Management University Singapore
6 shared publications - Ferdian Thung
Singapore Management University
5 shared publications - Jean-Pierre Lozi
INRIA, Paris, France
5 shared publications - Gilles Muller
INRIA France
4 shared publications - Lingxiao Jiang
Singapore Management University
4 shared publications
Latest Publications
- Open Access
- 14 November 2026
- Published by Association for Computing Machinery (ACM)
- p. 1700-1706
Detecting API Misuses Across Context Boundaries in Linux Kernel Drivers
- 14 November 2026
- Published by Association for Computing Machinery (ACM)
- p. 1700-1706
Open AccessDetecting API Misuses Across Context Boundaries in Linux Kernel Drivers
- Open Access
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 2973-2984
Generating Loop Invariants for Deductive Verification using Iterator Profiles
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 2973-2984
Open AccessGenerating Loop Invariants for Deductive Verification using Iterator Profiles
- Open Access
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 2254-2266
We Must Have Missed This Comment: Detecting and Repairing Stale Function References in Linux Kernel Comments
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 2254-2266
Open AccessWe Must Have Missed This Comment: Detecting and Repairing Stale Function References in Linux Kernel Comments
- Open Access
- 13 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 93-100
Tapestry: Revealing Wait-For Dependencies Between Application Threads
- 13 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 93-100
Open AccessTapestry: Revealing Wait-For Dependencies Between Application Threads
- Open Access
- 12 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 1
Automating Maintenance of the Linux Kernel: A Perspective over 20 Years (Keynote)
- 12 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 1
Open AccessAutomating Maintenance of the Linux Kernel: A Perspective over 20 Years (Keynote)
- Open Access
- 12 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 94-105
Understanding Linux Kernel Code through Formal Verification: A Case Study of the Task-Scheduler Function select_idle_core
- 12 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 94-105
Open AccessUnderstanding Linux Kernel Code through Formal Verification: A Case Study of the Task-Scheduler Function select_idle_core
- Open Access
- 12 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 1115-1130
FlexGuard: Fast Mutual Exclusion Independent of Subscription
- 12 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 1115-1130
Open AccessFlexGuard: Fast Mutual Exclusion Independent of Subscription
- Open Access
- 8 September 2025
- Published by Association for Computing Machinery (ACM)
- p. 167-173
The Impact of Kernel Asynchronous APIs on the Performance of a Kernel VPN
- 8 September 2025
- Published by Association for Computing Machinery (ACM)
- p. 167-173
Open AccessThe Impact of Kernel Asynchronous APIs on the Performance of a Kernel VPN
- Open Access
- 2 July 2025
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
- Vol. 34 (6) , 1-27
How Are We Detecting Inconsistent Method Names? An Empirical Study from Code Review Perspective
Proper naming of methods can make program code easier to understand, and thus enhance software maintainability. Yet, developers may use inconsistent names due to poor communication or a lack of familiarity with conventions within the software development lifecycle. To address this issue, much research effort has been invested into building automatic tools that can check for method name inconsistency and recommend consistent names. However, existing datasets generally do not provide precise details about why a method name was deemed improper and required to be changed. Such information can give useful hints on how to improve the recommendation of adequate method names. Accordingly, we construct a sample method-naming benchmark, ReName4J, by matching name changes with code reviews. We then present an empirical study on how state-of-the-art techniques perform in detecting or recommending consistent and inconsistent method names based on ReName4J. The main purpose of the study is to reveal a different perspective based on reviewed names rather than proposing a complete benchmark. We find that the existing techniques underperform on our review-driven benchmark, both in inconsistent checking and the recommendation. We further identify potential biases in the evaluation of existing techniques, which future research should consider thoroughly.
- 2 July 2025
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
- Vol. 34 (6) , 1-27
Open AccessHow Are We Detecting Inconsistent Method Names? An Empirical Study from Code Review Perspective
Proper naming of methods can make program code easier to understand, and thus enhance software maintainability. Yet, developers may use inconsistent names due to poor communication or a lack of familiarity with conventions within the software development lifecycle. To address this issue, much research effort has been invested into building automatic tools that can check for method name inconsistency and recommend consistent names. However, existing datasets generally do not provide precise details about why a method name was deemed improper and required to be changed. Such information can give useful hints on how to improve the recommendation of adequate method names. Accordingly, we construct a sample method-naming benchmark, ReName4J, by matching name changes with code reviews. We then present an empirical study on how state-of-the-art techniques perform in detecting or recommending consistent and inconsistent method names based on ReName4J. The main purpose of the study is to reveal a different perspective based on reviewed names rather than proposing a complete benchmark. We find that the existing techniques underperform on our review-driven benchmark, both in inconsistent checking and the recommendation. We further identify potential biases in the evaluation of existing techniques, which future research should consider thoroughly.
- 21 January 2025
- Published by Springer Nature
- p. 194-215
Should We Balance? Towards Formal Verification of the Linux Kernel Scheduler
- 21 January 2025
- Published by Springer Nature
- p. 194-215
Should We Balance? Towards Formal Verification of the Linux Kernel Scheduler