Re: sys_call_table not exported in 2.6 kernel
Date: Sun, 11 Sep 2005 08:12:25 +0200
> Does anyone what is the reason behind not exporting the
> "sys_call_table" symbol in the 2.6 kernel.
It was primarily used by modules changing the table,
which they are not supposed to as it causes problems
with race conditions and it becomes impossible to
safely remove a module (which becomes even worse if
you have been stacking different modules doing this).
Note to self: Don't try to allocate
256000 pages with GFP_KERNEL on x86.
- Re: [PATCH 3/6] secmark: export binary yes/no rather than kernel internal secid
... completely eliminate secmark from procfs+netlink and only export secctx ... For this reason, I think exporting the ...
- Re: Numeric change when exportingto text file
... -if it's a query, the SQL ... company to lose a valued customer. ... I'm looking for any type of reason or why ...
- Re: CSVDE export field order
... Our database programmer is exporting specific fields (sn, cn, ... etc.) from AD using csvde. ... reason when we moved that user to another ou and re-ran the csvde cmd ... this order (which messes up the rest of the perl script). ...
- Export table data to text file
... My little access 2k prog should be able to exchange data between 2 ... I thought that exporting the ... is probably the reason for importing problems on the 2nd machine's program. ...
- Re: Export Delimited issue
... I am not aware of the reason for this. ... One thing you could try, to resolve the problem, is to do this for each affected field in the query that you are exporting from... ... it only puts 2 decimals and drops off the 3rd. ...