From: Matthew Wilcox <willy@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
lsf-pc <lsf-pc@lists.linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] tracing the source of errors
Date: Thu, 8 Feb 2024 15:57:27 +0000 [thread overview]
Message-ID: <ZcT5540Bv7U8qoUa@casper.infradead.org> (raw)
In-Reply-To: <ZcP4GewZ9jPw5NbA@dread.disaster.area>
On Thu, Feb 08, 2024 at 08:37:29AM +1100, Dave Chinner wrote:
> ftrace using the function_graph tracer will emit the return values
> of the functions if you use it with the 'funcgraph-retval' option.
OK, but that may not be fine grained enough. Why is mmap() returning
-ENOMEM?
unsigned long do_mmap(struct file *file, unsigned long addr,
...
/* Careful about overflows.. */
len = PAGE_ALIGN(len);
if (!len)
return -ENOMEM;
...
/* Too many mappings? */
if (mm->map_count > sysctl_max_map_count)
return -ENOMEM;
So it can distinguish between mmap() returning ENOMEM because
get_unmapped_area() returned ENOMEM and do_mmap() returning ENOMEM of
its own accord (right?), but it can't tell you which of the above two
cases you hit. Or can it?
next prev parent reply other threads:[~2024-02-08 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 9:54 [LSF/MM/BPF TOPIC] tracing the source of errors Miklos Szeredi
2024-02-07 11:00 ` [Lsf-pc] " Jan Kara
2024-02-07 11:23 ` Miklos Szeredi
2024-02-07 12:00 ` Matthew Wilcox
2024-02-07 12:19 ` Miklos Szeredi
2024-02-08 20:47 ` Gabriel Krisman Bertazi
2024-02-07 19:29 ` Eric Sandeen
2024-02-08 20:39 ` Gabriel Krisman Bertazi
2024-02-07 17:16 ` Darrick J. Wong
2024-02-07 21:37 ` Dave Chinner
2024-02-08 9:09 ` Miklos Szeredi
2024-02-09 2:27 ` Dave Chinner
2024-02-08 15:57 ` Matthew Wilcox [this message]
2024-02-09 1:55 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZcT5540Bv7U8qoUa@casper.infradead.org \
--to=willy@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).