Bug 174941 - diskless clients forget to free initrd memory
diskless clients forget to free initrd memory
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: system-config-netboot (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Fabio Olive Leite
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-04 12:38 EST by Oleg Drokin
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: FC5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-09-21 22:11:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Proposed fix. (360 bytes, patch)
2005-12-04 12:38 EST, Oleg Drokin
no flags Details | Diff

  None (edit)
Description Oleg Drokin 2005-12-04 12:38:31 EST
Description of problem:

Diskless clients apparently forget to free initrd memory.
The problem lies in
/usr/share/system-config-netboot/diskless/diskless.init
that does umount of /.oldroot but forgets to do
/sbin/blockdev --flushbufs /dev/ram0
after that.
Comment 1 Oleg Drokin 2005-12-04 12:38:32 EST
Created attachment 121816 [details]
Proposed fix.
Comment 2 Jason Vas Dias 2005-12-05 14:01:45 EST
Thanks - patch applied in system-config-netboot-0.1.34+ .
Comment 3 Fedora Update System 2005-12-19 22:02:56 EST
From User-Agent: XML-RPC

system-config-netboot-0.1.34-1_FC3 has been pushed for FC3, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.
Comment 4 Fedora Update System 2005-12-19 22:03:37 EST
From User-Agent: XML-RPC

system-config-netboot-0.1.34-1_FC4 has been pushed for FC4, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.
Comment 5 Bill Nottingham 2006-09-21 22:11:44 EDT
Closing bugs in MODIFIED state from prior Fedora releases. If this bug persists
in a current Fedora release (such as Fedora Core 5 or later), please reopen and
set the version appropriately.

Note You need to log in before you can comment on or make changes to this bug.