| /linux-5.19.10/block/ |
| D | ioprio.c | 68 SYSCALL_DEFINE3(ioprio_set, int, which, int, who, int, ioprio) in SYSCALL_DEFINE3() argument
84 if (!who) in SYSCALL_DEFINE3()
87 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
92 if (!who) in SYSCALL_DEFINE3()
95 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
109 uid = make_kuid(current_user_ns(), who); in SYSCALL_DEFINE3()
112 if (!who) in SYSCALL_DEFINE3()
129 if (who) in SYSCALL_DEFINE3()
167 SYSCALL_DEFINE2(ioprio_get, int, which, int, who) in SYSCALL_DEFINE2() argument
179 if (!who) in SYSCALL_DEFINE2()
[all …]
|
| D | sed-opal.c | 1508 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-5.19.10/drivers/gpu/drm/i915/selftests/ |
| D | scatterlist.c | 44 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-5.19.10/arch/s390/kvm/ |
| D | trace-s390.h | 126 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-5.19.10/kernel/ |
| D | sys.c | 210 SYSCALL_DEFINE3(setpriority, int, which, int, who, int, niceval) in SYSCALL_DEFINE3() argument
232 if (who) in SYSCALL_DEFINE3()
233 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
240 if (who) in SYSCALL_DEFINE3()
241 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
251 uid = make_kuid(cred->user_ns, who); in SYSCALL_DEFINE3()
253 if (!who) in SYSCALL_DEFINE3()
280 SYSCALL_DEFINE2(getpriority, int, which, int, who) in SYSCALL_DEFINE2() argument
295 if (who) in SYSCALL_DEFINE2()
296 p = find_task_by_vpid(who); in SYSCALL_DEFINE2()
[all …]
|
| /linux-5.19.10/Documentation/process/ |
| D | 1.Intro.rst | 64 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 …]
|
| D | 5.Posting.rst | 31 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
221 A third kind of tag is used to document who was involved in the development of
252 - Reported-by: names a user who reported a problem which is fixed by this
254 people who test our code and let us know when things do not work
291 When mailing patches, it is important to send copies to anybody who might
[all …]
|
| D | 3.Early-stage.rst | 139 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
161 developers who have no real interest in the code you are modifying.
|
| D | management-style.rst | 7 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
|
| D | embargoed-hardware-issues.rst | 35 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
296 Subscription is handled by the response teams. Disclosed parties who want
|
| D | development-process.rst | 24 accessible to those who are not intimately familiar with Linux kernel
|
| /linux-5.19.10/arch/ia64/kernel/ |
| D | sys_ia64.c | 71 ia64_getpriority (int which, int who) in ia64_getpriority() argument
75 prio = sys_getpriority(which, who); in ia64_getpriority()
|
| /linux-5.19.10/Documentation/block/ |
| D | ioprio.rst | 90 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-5.19.10/arch/x86/kernel/ |
| D | e820.c | 203 void __init e820__print_table(char *who) in e820__print_table() argument
209 who, in e820__print_table()
1262 char *who = "BIOS-e820"; in e820__memory_setup_default() local
1276 who = "BIOS-88"; in e820__memory_setup_default()
1279 who = "BIOS-e801"; in e820__memory_setup_default()
1290 return who; in e820__memory_setup_default()
1300 char *who; in e820__memory_setup() local
1305 who = x86_init.resources.memory_setup(); in e820__memory_setup()
1311 e820__print_table(who); in e820__memory_setup()
|
| /linux-5.19.10/include/linux/ |
| D | resource.h | 10 void getrusage(struct task_struct *p, int who, struct rusage *ru);
|
| /linux-5.19.10/fs/ |
| D | fcntl.c | 117 int who = arg, ret = 0; in f_setown() local
120 if (who < 0) { in f_setown()
122 if (who == INT_MIN) in f_setown()
126 who = -who; in f_setown()
130 if (who) { in f_setown()
131 pid = find_vpid(who); in f_setown()
|
| /linux-5.19.10/fs/nfsd/ |
| D | acl.h | 44 __be32 nfs4_acl_write_who(struct xdr_stream *xdr, int who);
|
| /linux-5.19.10/Documentation/admin-guide/sysctl/ |
| D | user.rst | 25 the user in the user namespace who created the object and
29 who created user namespaces the creation of the object happens
|
| /linux-5.19.10/drivers/virt/coco/sev-guest/ |
| D | Kconfig | 9 the PSP without risk from a malicious hypervisor who wishes to read,
|
| /linux-5.19.10/Documentation/devicetree/bindings/eeprom/ |
| D | at25.yaml | 18 # There are multiple known vendors who manufacture EEPROM chips compatible
22 # "atmel,at25" part and should be fixed by somebody who knows vendor and
|
| /linux-5.19.10/Documentation/scsi/ |
| D | FlashPoint.rst | 93 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-5.19.10/arch/sparc/kernel/ |
| D | windows.c | 113 void try_to_clear_window_buffer(struct pt_regs *regs, int who) in try_to_clear_window_buffer() argument
|
| /linux-5.19.10/arch/x86/include/asm/e820/ |
| D | api.h | 21 extern void e820__print_table(char *who);
|
| /linux-5.19.10/Documentation/arm/samsung-s3c24xx/ |
| D | h1940.rst | 38 Thanks to the many others who have also provided support.
|
| /linux-5.19.10/Documentation/vm/ |
| D | page_owner.rst | 4 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
102 See the result about who allocated each page
|