similar to: [klibc:master] kinit: Fix capabilities alternate read/ write io without flush

Commit-ID: 163920f31f98db13f4e37796bb92f0844e7aaf45 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=163920f31f98db13f4e37796bb92f0844e7aaf45 Author: maximilian attems <max at stro.at> AuthorDate: Tue, 29 May 2012 18:58:31 +0200 Committer: maximilian attems <max at stro.at> CommitDate: Tue, 29 May 2012 19:03:08 +0200 [klibc] capabilities: Use fflush() instead

This patch adds the ability to kinit to allow the dropping of POSIX capabilities. kinit is modified by this change, such that it understands the new kernel command line "drop_capabilities=" that specifies a comma separated list of capability names that should be dropped before switching over to the next init in the boot strap (typically on the root disk). When processing capabilities

From: Maciej ?enczykowski <maze at google.com> Google-Bug-Id: 9093057 Change-Id: I75a6cdc0619ae95a0220e8387aa54920701f6209 --- usr/kinit/capabilities.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/usr/kinit/capabilities.c b/usr/kinit/capabilities.c index e743a70fec0f..4e0456ee7407 100644 --- a/usr/kinit/capabilities.c +++ b/usr/kinit/capabilities.c @@ -172,9

This patchset applies to klibc mainline. As is it will probably collide with Maximilian's recent patch to rename run-init to switch_root posted last week. To boot an untrusted environment with certain capabilities locked out, we'd like to be able to drop the capabilities up front from early userspace, before we actually transition onto the root volume. This patchset implements this by

Hello Tom, > I took a look at lib/CodeGen/SelectionDAG/LegalizeDAG.cpp and it > doesn't look like there is an Expand operation implemented for > ISD::Constant. I think you'll either need implement Expand for > ISD::Constant or Custom lower it in your backend. thank you for that information. This exactly is what I feared. Well I did some more mostly unguided hacking and these

hello hpa, have been sitting too long on them, nothing exciting, please pull: git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks with the following shortlog: maximilian attems (8): [klibc] grp.h: Add declaration of getgrgid(), getgrnam() [klibc] getgrgid, getgrnam include grp.h [klibc] getpwnam, getpwuid include pwd.h [klibc] ctype.h declare char classification

hello hpa, current chroot util stands out as broken and found an old nfsmount commit on a stray testbox in our institue. thanks for taking a look! maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: maximilian attems (4): [klibc] malloc fix compile with DEBUG_MALLOC [klibc] README: add klibc email [klibc] nfsmount: improve error message [klibc]

hello hpa, please pull latest git pull git://git.debian.org/~maks/klibc.git maks forgot to ask to keep git port open for our boxes at university, thus moved my tree over too the alioth box. for the changes maximilian attems (4): [klibc] klibc/socketcalls/.gitignore addition [klibc] elf.h add support for st_info field [klibc] remove local insmod.c copy [klibc] ipconfig

hello hpa, nothing particular stands out, just syncing with latest Debian upload and subsequent patch emails. please review merge or nack. thanks :) maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md assembly if mdX exists Colin Watson (1): [klibc] mount/umount FUSE support Harald Jenny (1): [klibc] fstype:

hello hpa, due to arch x86 merge and stricter linitian. lintian complained about empty dirs in the -dev headers package. hadn't seen that warning yet, so below is the fix. ah and that other patch was in some other branch.. please pull latest unless sam has a reservation git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md

Commit-ID: 25a66fa8d8623fae267f6807b56438cd7c40e034 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=25a66fa8d8623fae267f6807b56438cd7c40e034 Author: maximilian attems <max at stro.at> AuthorDate: Wed, 21 Aug 2013 17:31:25 +0200 Committer: maximilian attems <max at stro.at> CommitDate: Wed, 21 Aug 2013 17:32:16 +0200 README.klibc: update build information It

this is just on the common path, need to checkout others too, but a start: commit 5501109f6597f2bbed17a264b247c36220362dfb Author: maximilian attems <max at stro.at> Date: Mon Apr 26 08:07:51 2010 +0200 [klibc] ipconfig: Fix valgrind errors valgrind was rightfully complaining on ipconfig eth0: ERROR SUMMARY: 5 errors from 4 contexts (suppressed: 0 from 0) all

On Wed, Aug 21, 2013 at 06:48:08PM +0200, maximilian attems wrote: > On Wed, Aug 21, 2013 at 06:03:41PM +0200, leroy christophe wrote: > > > > Note that step B is working well. > > It is step C, the 'make install', which fails. > > right, it is the toplevel Makefile one needs to poke for the target. > see belows proper patch: >From

Add some semi-useful error message, as printing the failing dir or file seems not really advisable after that error. Signed-off-by: maximilian attems <max at stro.at> --- usr/utils/ln.c | 20 +++++++++++++++----- 1 files changed, 15 insertions(+), 5 deletions(-) diff --git a/usr/utils/ln.c b/usr/utils/ln.c index e826eb8..257b33f 100644 --- a/usr/utils/ln.c +++ b/usr/utils/ln.c @@ -9,7

From: maximilian attems <max at stro.at> On review of klibc dash changes: "Hmm, this breaks the non-glibc case. You're now returning a pointer to a string on the stack which is illegal." Herbert Xu Use upstream dash way. Signed-off-by: maximilian attems <max at stro.at> Cc: Herbert Xu <herbert at gondor.apana.org.au> --- usr/dash/cd.c | 7 ++++--- 1 files

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

Commit-ID: d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Author: Steve McIntyre <steve at einval.com> AuthorDate: Fri, 29 Jun 2012 18:13:34 +0100 Committer: maximilian attems <max at stro.at> CommitDate: Sun, 1 Jul 2012 22:51:00 +0200 [klibc] arm/setjmp.S: fix longjmp

From: Matt Fleming <matt at console-pimps.org> Uncovered a bug in avr32 signal handling, might come handy in testing other archs signal. Signed-off-by: Matt Fleming <matt at console-pimps.org> Signed-off-by: maximilian attems <max at stro.at> --- Seen on lmkl, any objections to add your test to klibc: http://git.kernel.org/?p=libs/klibc/klibc.git;a=summary We know archs were

When porting patches from dash git to klibc git, where dash has a different directory structure those switches are handy: Exported with format-patch on dash side and used am as import for klibc side. Signed-off-by: maximilian attems <max at stro.at> --- Documentation/git-am.txt | 5 ++++- git-am.sh | 4 +++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

Package: logcheck wanted to work on #195935, but found a less than funny issue, easy to reproduce: * remove some lines in front of your logfile * invoke logcheck you'll get a big email with all not matching lines from that log. not setting that to high priority because you are getting also the newer loglines. don't know if i find time that weekend. wanted to document it anyways. a++