[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220905151633.04081816@gandalf.local.home>
Date: Mon, 5 Sep 2022 15:16:33 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Nadav Amit <nadav.amit@...il.com>
Cc: Mel Gorman <mgorman@...e.de>,
Kent Overstreet <kent.overstreet@...ux.dev>,
Peter Zijlstra <peterz@...radead.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>,
Johannes Weiner <hannes@...xchg.org>, roman.gushchin@...ux.dev,
dave@...olabs.net, Matthew Wilcox <willy@...radead.org>,
liam.howlett@...cle.com, void@...ifault.com, juri.lelli@...hat.com,
ldufour@...ux.ibm.com, Peter Xu <peterx@...hat.com>,
David Hildenbrand <david@...hat.com>,
Jens Axboe <axboe@...nel.dk>, mcgrof@...nel.org,
masahiroy@...nel.org, nathan@...nel.org, changbin.du@...el.com,
ytcoode@...il.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, bsegall@...gle.com, bristot@...hat.com,
vschneid@...hat.com, cl@...ux.com, penberg@...nel.org,
iamjoonsoo.kim@....com, 42.hyeyoo@...il.com, glider@...gle.com,
Marco Elver <elver@...gle.com>, dvyukov@...gle.com,
Shakeel Butt <shakeelb@...gle.com>,
Muchun Song <songmuchun@...edance.com>,
Arnd Bergmann <arnd@...db.de>, jbaron@...mai.com,
David Rientjes <rientjes@...gle.com>, minchan@...gle.com,
kaleshsingh@...gle.com, kernel-team@...roid.com,
Linux MM <linux-mm@...ck.org>, iommu@...ts.linux.dev,
kasan-dev@...glegroups.com, io-uring@...r.kernel.org,
linux-arch <linux-arch@...r.kernel.org>,
xen-devel@...ts.xenproject.org, linux-bcache@...r.kernel.org,
linux-modules@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 00/30] Code tagging framework and applications
On Mon, 5 Sep 2022 11:44:55 -0700
Nadav Amit <nadav.amit@...il.com> wrote:
> I would note that I have a solution in the making (which pretty much works)
> for this matter, and does not require any kernel changes. It produces a
> call stack that leads to the code that lead to syscall failure.
>
> The way it works is by using seccomp to trap syscall failures, and then
> setting ftrace function filters and kprobes on conditional branches,
> indirect branch targets and function returns.
Ooh nifty!
>
> Using symbolic execution, backtracking is performed and the condition that
> lead to the failure is then pin-pointed.
>
> I hope to share the code soon.
Looking forward to it.
-- Steve
Powered by blists - more mailing lists