[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230619111635.ls26ojl7patttkiu@moria.home.lan>
Date: Mon, 19 Jun 2023 07:16:35 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Mark Rutland <mark.rutland@....com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-bcachefs@...r.kernel.org,
Christopher James Halse Rogers <raof@...ntu.com>
Subject: Re: [PATCH 28/32] stacktrace: Export stack_trace_save_tsk
On Mon, Jun 19, 2023 at 10:10:56AM +0100, Mark Rutland wrote:
> On Tue, May 09, 2023 at 12:56:53PM -0400, Kent Overstreet wrote:
> > From: Christopher James Halse Rogers <raof@...ntu.com>
> >
> > The bcachefs module wants it, and there doesn't seem to be any
> > reason it shouldn't be exported like the other functions.
>
> What is the bcachefs module using this for?
>
> Is that just for debug purposes? Assuming so, mentioning that in the commit
> message would be helpful.
Yes, the output ends up in debugfs.
Powered by blists - more mailing lists