Home
last modified time | relevance | path

Searched refs:who (Results 1 – 25 of 252) sorted by relevance

1234567891011

/Linux-v5.15/block/
Dioprio.c93 SYSCALL_DEFINE3(ioprio_set, int, which, int, who, int, ioprio) in SYSCALL_DEFINE3() argument
109 if (!who) in SYSCALL_DEFINE3()
112 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
117 if (!who) in SYSCALL_DEFINE3()
120 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
134 uid = make_kuid(current_user_ns(), who); in SYSCALL_DEFINE3()
137 if (!who) in SYSCALL_DEFINE3()
154 if (who) in SYSCALL_DEFINE3()
192 SYSCALL_DEFINE2(ioprio_get, int, which, int, who) in SYSCALL_DEFINE2() argument
204 if (!who) in SYSCALL_DEFINE2()
[all …]
Dsed-opal.c1508 else if (session->who != OPAL_ADMIN1 && !session->sum) in start_auth_opal_session()
1510 session->who - 1); in start_auth_opal_session()
1562 uid[7] = session->who; in internal_activate_user()
1689 if (usr->who != OPAL_ADMIN1) { in set_new_pw()
1694 cpin_uid[7] = usr->who; in set_new_pw()
1738 user_uid[7] = lkul->session.who; in add_user_to_lr()
2309 if (lk_unlk->session.who < OPAL_USER1 || in opal_add_user_to_lr()
2310 lk_unlk->session.who > OPAL_USER9) { in opal_add_user_to_lr()
2312 lk_unlk->session.who); in opal_add_user_to_lr()
2403 if (lk_unlk->session.who > OPAL_USER9) in opal_lock_unlock()
[all …]
/Linux-v5.15/drivers/gpu/drm/i915/selftests/
Dscatterlist.c44 const char *who, in expect_pfn_sg() argument
57 __func__, who, pfn, page_to_pfn(page)); in expect_pfn_sg()
63 __func__, who, npages * PAGE_SIZE, sg->length); in expect_pfn_sg()
67 if (igt_timeout(timeout, "%s timed out\n", who)) in expect_pfn_sg()
74 __func__, who, pt->end, pfn); in expect_pfn_sg()
82 const char *who, in expect_pfn_sg_page_iter() argument
94 __func__, who, pfn, page_to_pfn(page)); in expect_pfn_sg_page_iter()
98 if (igt_timeout(timeout, "%s timed out\n", who)) in expect_pfn_sg_page_iter()
105 __func__, who, pt->end, pfn); in expect_pfn_sg_page_iter()
113 const char *who, in expect_pfn_sgtiter() argument
[all …]
/Linux-v5.15/arch/s390/kvm/
Dtrace-s390.h126 TP_PROTO(__u64 type, __u32 parm, __u64 parm64, int who),
127 TP_ARGS(type, parm, parm64, who),
133 __field(int, who)
140 __entry->who = who;
144 (__entry->who == 1) ? " (from kernel)" :
145 (__entry->who == 2) ? " (from user)" : "",
/Linux-v5.15/kernel/
Dsys.c203 SYSCALL_DEFINE3(setpriority, int, which, int, who, int, niceval) in SYSCALL_DEFINE3() argument
226 if (who) in SYSCALL_DEFINE3()
227 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
234 if (who) in SYSCALL_DEFINE3()
235 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
243 uid = make_kuid(cred->user_ns, who); in SYSCALL_DEFINE3()
245 if (!who) in SYSCALL_DEFINE3()
273 SYSCALL_DEFINE2(getpriority, int, which, int, who) in SYSCALL_DEFINE2() argument
289 if (who) in SYSCALL_DEFINE2()
290 p = find_task_by_vpid(who); in SYSCALL_DEFINE2()
[all …]
/Linux-v5.15/Documentation/process/
D1.Intro.rst64 those products attractive to Linux users. Embedded systems vendors, who
67 other software vendors who base their products on Linux have a clear
92 experience behind it. A developer who does not understand the kernel
93 community's ways (or, worse, who tries to flout or circumvent them) will
95 being helpful to those who are trying to learn, has little time for those
96 who will not listen or who do not care about the development process.
98 It is hoped that those who read this document will be able to avoid that
101 community is always in need of developers who will help to make the kernel
102 better; the following text should help you - or those who work for you -
115 Amanda McPherson, who saw the value of this effort and made it all happen.
[all …]
D5.Posting.rst31 patches which are known to be half-baked, but those who do will come in
111 users who are engaging in the noble work of tracking down problems.
145 enough for a reader who sees it with no other context to figure out the
166 These include subsystem maintainers and reviewers who need to decide
170 chasing, users who want to know how the kernel has changed, and more. A
184 general, the more you can put yourself into the shoes of everybody who will
237 - Reported-by: names a user who reported a problem which is fixed by this
239 people who test our code and let us know when things do not work
276 When mailing patches, it is important to send copies to anybody who might
285 - Other developers who have been working in the same area - especially
[all …]
D3.Early-stage.rst139 MAINTAINERS file may, in fact, not be the person who is actually acting in
140 that role currently. So, when there is doubt about who to contact, a
141 useful trick is to use git (and "git log" in particular) to see who is
142 currently active within the subsystem of interest. Look at who is writing
143 patches, and who, if anybody, is attaching Signed-off-by lines to those
144 patches. Those are the people who will be best placed to help with a new
156 command line, it will list the maintainers who should probably receive
160 who have no real interest in the code you are modifying.
Dmanagement-style.rst7 on who you ask) management style for the linux kernel. It's meant to
18 lead persons, not the people who do traditional management inside
111 This preemptive admission of incompetence might also make the people who
176 trust somebody who is so clearly hiding their true character.
196 Suck up to them, because they are the people who will make your job
225 person who lost their whole 36GB porn-collection because of your
229 Then make the developer who really screwed up (if you can find them) know
232 importantly, they're also likely the person who can fix it. Because, let's
237 glory, because you're the one who gets to say "I screwed up". And if
265 without making it painful to the recipient, who just thinks you're being
Dembargoed-hardware-issues.rst35 is a private list of security officers who will help you to coordinate an
47 vendor, we welcome contact from researchers or individuals who have
98 The hardware security team identifies the developers (domain experts) who
138 developers (domain experts) who should be informed initially about the
152 entities who have already been, or should be, informed about the issue.
158 - The disclosed entities can be contacted to name experts who should
241 organizations, who can answer questions about or provide guidance on the
295 Subscription is handled by the response teams. Disclosed parties who want
Ddevelopment-process.rst24 accessible to those who are not intimately familiar with Linux kernel
D2.Process.rst59 allowed, but such occasions are rare; developers who try to merge new
219 There is exactly one person who can merge patches into the mainline kernel
230 who has overall responsibility for the code within that subsystem. These
232 of the kernel they manage; they are the ones who will (usually) accept a
372 Among the kernel developers who do not use git, the most popular choice is
398 represent a potential hazard to developers, who risk getting buried under a
415 development community comes together as a whole; developers who avoid this
427 without changing the email subject line) and the people who are
441 questions. Some developers can get impatient with people who clearly
453 beginning developers to go wrong. Somebody who asks a networking-related
[all …]
/Linux-v5.15/Documentation/vm/
Dpage_owner.rst4 page owner: Tracking about who allocated each page
10 page owner is for the tracking about who allocated each page.
18 using it for analyzing who allocate each page is rather complex. We need
88 See the result about who allocated each page
/Linux-v5.15/arch/ia64/kernel/
Dsys_ia64.c71 ia64_getpriority (int which, int who) in ia64_getpriority() argument
75 prio = sys_getpriority(which, who); in ia64_getpriority()
/Linux-v5.15/Documentation/block/
Dioprio.rst90 static inline int ioprio_set(int which, int who, int ioprio)
92 return syscall(__NR_ioprio_set, which, who, ioprio);
95 static inline int ioprio_get(int which, int who)
97 return syscall(__NR_ioprio_get, which, who);
/Linux-v5.15/arch/x86/kernel/
De820.c203 void __init e820__print_table(char *who) in e820__print_table() argument
209 who, in e820__print_table()
1243 char *who = "BIOS-e820"; in e820__memory_setup_default() local
1257 who = "BIOS-88"; in e820__memory_setup_default()
1260 who = "BIOS-e801"; in e820__memory_setup_default()
1271 return who; in e820__memory_setup_default()
1281 char *who; in e820__memory_setup() local
1286 who = x86_init.resources.memory_setup(); in e820__memory_setup()
1292 e820__print_table(who); in e820__memory_setup()
/Linux-v5.15/include/linux/
Dresource.h10 void getrusage(struct task_struct *p, int who, struct rusage *ru);
/Linux-v5.15/fs/nfsd/
Dacl.h44 __be32 nfs4_acl_write_who(struct xdr_stream *xdr, int who);
/Linux-v5.15/fs/
Dfcntl.c118 int who = arg, ret = 0; in f_setown() local
121 if (who < 0) { in f_setown()
123 if (who == INT_MIN) in f_setown()
127 who = -who; in f_setown()
131 if (who) { in f_setown()
132 pid = find_vpid(who); in f_setown()
/Linux-v5.15/Documentation/admin-guide/sysctl/
Duser.rst25 the user in the user namespace who created the object and
29 who created user namespaces the creation of the object happens
/Linux-v5.15/Documentation/scsi/
DFlashPoint.rst93 caused grief for many people who inadvertently purchased a system expecting
100 made available, and that Linux users who mistakenly ordered systems with
104 assist the people who initially purchased a FlashPoint for a supported
105 operating system and then later decided to run Linux, or those who had
125 are people at BusLogic who would rather not release the details of the
/Linux-v5.15/arch/x86/include/asm/e820/
Dapi.h21 extern void e820__print_table(char *who);
/Linux-v5.15/arch/sparc/kernel/
Dwindows.c113 void try_to_clear_window_buffer(struct pt_regs *regs, int who) in try_to_clear_window_buffer() argument
/Linux-v5.15/Documentation/arm/samsung-s3c24xx/
Dh1940.rst38 Thanks to the many others who have also provided support.
/Linux-v5.15/tools/testing/selftests/net/mptcp/
Dmptcp_sockopt.sh233 who=$2
239 echo "Created $name (size $size KB) containing data sent by $who"

1234567891011