From: Greg KH <greg@kroah.com>
To: "孙世龙 sunshilong" <sunshilong369@gmail.com>
Cc: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
Kernelnewbies@kernelnewbies.org
Subject: Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
Date: Sat, 27 Jun 2020 09:05:03 +0200 [thread overview]
Message-ID: <20200627070503.GA264737@kroah.com> (raw)
In-Reply-To: <CAAvDm6ZNRhRB7yO+feuxkFPfDD+6F0NN0G7etr8eVCtfe2aRJg@mail.gmail.com>
On Sat, Jun 27, 2020 at 02:00:50PM +0800, 孙世龙 sunshilong wrote:
> Hi, Greg KH
> Thank you for your patience and your help.
> >What code is causing that failure by asking for memory that you do not
> >have? Please fix that up, the core kernel should be fine.
>
> >Then fix your broken driver that is asking for so much memory on a
> >system that does not have it. Do you have a pointer to your driver
> >anywhere so we can review it?
>
> >Applications do not allocate kernel memory at all, that's up to a kernel
> >driver. Userspace does things in totally different ways.
> Not at the driver load time, but the load time of the real-time
> process(i.e. **before the entry of the main() function**).It invokes
> a systemcall which internally invokes kmalloc(). I'd show you the
> related code and the call trace info below.
<snip>
> Kzalloc() is invoked by xnheap_init() in the xenomai source code(see
> https://gitlab.denx.de/Xenomai/xenomai/-/blob/v3.1/kernel/cobalt/heap.c).
Hah, cobalt, that's your problem.
Seriously, that's a crazy architecture, one that turned out not to
really work well compared to what ended up getting merged upstream.
As you are really messing with how Linux works with this add-on, I
strongly suggest you get support from the Xenomai developers as they are
the only ones that can support you. The Linux kernel community can't,
sorry.
Best of luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-06-27 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 8:30 Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()? 孙世龙 sunshilong
2020-06-26 14:13 ` Greg KH
2020-06-26 15:36 ` 孙世龙 sunshilong
2020-06-26 17:22 ` Valdis Klētnieks
2020-06-27 5:16 ` 孙世龙 sunshilong
2020-06-27 5:23 ` Greg KH
2020-06-27 6:00 ` 孙世龙 sunshilong
2020-06-27 7:05 ` Greg KH [this message]
2020-06-27 5:05 ` Greg KH
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=20200627070503.GA264737@kroah.com \
--to=greg@kroah.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=sunshilong369@gmail.com \
--cc=valdis.kletnieks@vt.edu \
/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).