| /linux-4.1.27/fs/nilfs2/ |
| D | segbuf.h | 172 void nilfs_clear_logs(struct list_head *logs);
173 void nilfs_truncate_logs(struct list_head *logs,
175 int nilfs_write_logs(struct list_head *logs, struct the_nilfs *nilfs);
176 int nilfs_wait_on_logs(struct list_head *logs);
177 void nilfs_add_checksums_on_logs(struct list_head *logs, u32 seed);
179 static inline void nilfs_destroy_logs(struct list_head *logs) in nilfs_destroy_logs() argument
181 nilfs_truncate_logs(logs, NULL); in nilfs_destroy_logs()
|
| D | segbuf.c | 274 void nilfs_clear_logs(struct list_head *logs) in nilfs_clear_logs() argument
278 list_for_each_entry(segbuf, logs, sb_list) in nilfs_clear_logs()
282 void nilfs_truncate_logs(struct list_head *logs, in nilfs_truncate_logs() argument
287 segbuf = list_prepare_entry(last, logs, sb_list); in nilfs_truncate_logs()
288 list_for_each_entry_safe_continue(segbuf, n, logs, sb_list) { in nilfs_truncate_logs()
295 int nilfs_write_logs(struct list_head *logs, struct the_nilfs *nilfs) in nilfs_write_logs() argument
300 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_write_logs()
308 int nilfs_wait_on_logs(struct list_head *logs) in nilfs_wait_on_logs() argument
313 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_wait_on_logs()
326 void nilfs_add_checksums_on_logs(struct list_head *logs, u32 seed) in nilfs_add_checksums_on_logs() argument
[all …]
|
| D | segment.c | 1333 static void nilfs_free_incomplete_logs(struct list_head *logs, in nilfs_free_incomplete_logs() argument
1340 segbuf = NILFS_FIRST_SEGBUF(logs); in nilfs_free_incomplete_logs()
1357 list_for_each_entry_continue(segbuf, logs, sb_list) { in nilfs_free_incomplete_logs()
1387 static void nilfs_cancel_segusage(struct list_head *logs, struct inode *sufile) in nilfs_cancel_segusage() argument
1392 segbuf = NILFS_FIRST_SEGBUF(logs); in nilfs_cancel_segusage()
1398 list_for_each_entry_continue(segbuf, logs, sb_list) { in nilfs_cancel_segusage()
1679 static void nilfs_abort_logs(struct list_head *logs, int err) in nilfs_abort_logs() argument
1685 if (list_empty(logs)) in nilfs_abort_logs()
1688 list_for_each_entry(segbuf, logs, sb_list) { in nilfs_abort_logs()
1723 LIST_HEAD(logs); in nilfs_segctor_abort_construction()
[all …]
|
| /linux-4.1.27/tools/testing/selftests/ftrace/ |
| D | Makefile | 8 rm -rf logs/*
|
| D | ftracetest | 95 LOG_DIR=$TOP_DIR/logs/`date +%Y%m%d-%H%M%S`/
|
| /linux-4.1.27/Documentation/s390/ |
| D | s390dbf.txt | 12 One purpose of this is to inspect the debug logs after a production system crash
15 it is possible to look at the debug logs on a live system via the Linux
54 The debug logs can be inspected in a live system through entries in
68 All debug logs have an actual debug level (range from 0 to 6).
401 Views to the debug logs can be investigated through reading the corresponding
471 's390dbf' to display all the debug logs. With this tool it will be possible
472 to investigate the debug logs on a live system and with a memory dump after
477 One last possibility to investigate the debug logs at a live
480 It is possible to find the anker of the debug-logs through
485 a global variable with the pointer to the debug-logs. Following
[all …]
|
| /linux-4.1.27/drivers/net/wireless/zd1211rw/ |
| D | Kconfig | 17 messages being saved to your kernel logs, which may help debug any
|
| /linux-4.1.27/security/tomoyo/ |
| D | Kconfig | 37 audit logs that the kernel can hold on memory.
39 If you don't need audit logs, you may set this value to 0.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | nilfs2.txt | 183 of logs. Each log is composed of summary information blocks, payload
223 The logs include regular files, directory files, symbolic link files
235 The following figure shows a typical organization of the logs:
243 into multiple logs. The sequence of logs that should be treated as
|
| D | xfs.txt | 144 Valid sizes for version 1 and version 2 logs are 16384 (16k)
145 and 32768 (32k). Valid sizes for version 2 logs also
150 The default value for for version 1 logs is 32768, while the
151 default value for version 2 logs is MAX(32768, log_sunit).
|
| D | f2fs.txt | 94 - Support multi-head logs for static/dynamic hot and cold data separation
119 active_logs=%u Support configuring the number of active logs. In the
120 current design, f2fs supports only 2, 4, and 6 logs.
531 At runtime, F2FS manages six active logs inside "Main" area: Hot/Warm/Cold node
555 logs from different zones as much as possible, since FTL can write the data in
556 the active logs into one allocation unit according to its mapping granularity.
|
| /linux-4.1.27/Documentation/ |
| D | debugging-modules.txt | 10 In the past a debugging message which would fill people's logs was
|
| D | debugging-via-ohci1394.txt | 35 this facility proved most useful for examining long debugs logs in the printk
93 Load the firewire-ohci module and check your kernel logs.
|
| D | ramoops.txt | 10 Ramoops is an oops/panic logger that writes its logs to RAM before the system
|
| D | vfio.txt | 399 /* Enable IO for the affected PE and collect logs. Usually, the
401 * as logs for further analysis.
|
| D | parport.txt | 240 The kernel messages that parport_pc logs give an indication of which
|
| D | remoteproc.txt | 258 * the remote processor will be writing logs.
|
| D | edac.txt | 383 If logging for UEs and CEs are enabled then system logs will have
|
| D | DMA-API.txt | 643 option, as it can easily flood your logs.
|
| D | DMA-API-HOWTO.txt | 508 kernel logs when the DMA controller hardware detects violation of the
|
| D | SubmittingPatches | 691 especially useful for people who might be searching the commit logs
|
| /linux-4.1.27/Documentation/watchdog/ |
| D | wdt.txt | 21 The third interface logs kernel messages on additional alert events.
|
| D | hpwdt.txt | 47 confused" message in the logs or if the system gets into a hung state, then
|
| /linux-4.1.27/drivers/platform/chrome/ |
| D | Kconfig | 32 devices. It can be used to store away console logs and crash
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | README.DAC960 | 413 The following annotated logs demonstrate the controller configuration and and
418 logical drives, one RAID-5 and one RAID-6. Note that these logs are from an
453 driver logs the following console status messages indicating that Logical
505 Within 10 seconds of this command the driver logs the initiation of the
553 Finally, the rebuild completes successfully. The driver logs the status of the
585 The following annotated logs demonstrate the controller configuration and and
590 logical drives, one RAID-5 and one RAID-6. Note that these logs are from an
625 driver logs the following console status messages:
688 Finally, the rebuild completes successfully. The driver logs the status of the
736 the console by the driver. Within 60 seconds of this command the driver logs:
|
| /linux-4.1.27/Documentation/laptops/ |
| D | sony-laptop.txt | 15 subsystem. See the logs of /proc/bus/input/devices to find out what those
93 In your kernel logs you will find the list of all ACPI methods
|
| D | sonypi.txt | 54 or kernel logs)
|
| /linux-4.1.27/Documentation/networking/ |
| D | vortex.txt | 86 of output in your system logs. debug=1 is default.
405 o Any kernel logs which are produced. The more the merrier.
411 To ensure that all kernel logs are available, add the
432 send all logs to the maintainer.
|
| D | generic-hdlc.txt | 123 "private" command to see port's packet descriptor rings (in kernel logs):
|
| D | netconsole.txt | 12 This module logs kernel printk messages over UDP allowing debugging of
|
| D | ip-sysctl.txt | 517 in your logs, but investigation shows that they occur
526 SYN flood warnings in logs not being really flooded, your server
|
| /linux-4.1.27/Documentation/i2c/ |
| D | i2c-stub | 15 arrays in memory. It will also spam the kernel logs for every command it
|
| /linux-4.1.27/drivers/usb/dwc2/ |
| D | Kconfig | 97 non-periodic transfers, but of course the debug logs will be
|
| /linux-4.1.27/Documentation/dvb/ |
| D | bt8xx.txt | 56 In your logs see f. ex.: dst_get_device_id: Recognize [DSTMCI].
|
| D | avermedia.txt | 285 dmesg and the system logs, it does not appear to affect the
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.gigaset | 412 for his work and logs to get unimodem mode working
414 for his logs and patches to get cx 100 working
420 and all the other people who sent logs and other information.
|
| D | INTERFACE.CAPI | 341 If the lowest bit of showcapimsgs is set, kernelcapi logs controller and
354 length are logged. Otherwise, kernelcapi logs a readable representation of
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | boot-options.txt | 19 error logs.
21 Don't make logs for corrected errors. All events reported
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pcieaer-howto.txt | 113 internally processes and logs the error message in its PCI Express
173 correctable error status register accordingly and logs these errors.
|
| /linux-4.1.27/Documentation/trace/ |
| D | mmiotrace.txt | 162 - replaying MMIO logs, i.e., re-executing the recorded writes
|
| /linux-4.1.27/drivers/md/ |
| D | Kconfig | 341 shared storage logs) or experimental logs can be implemented
|
| /linux-4.1.27/drivers/media/usb/pwc/ |
| D | philips.txt | 185 'trace' of some of the calls the module makes; it logs all items in your
|
| /linux-4.1.27/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 214 * - bunch of other stuff, will fill in logs later.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 402 with megaraid_sas. Thanks to RB for providing the logs and
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 26 that are auditing their logs closely may want to set it to a lower
|
| /linux-4.1.27/init/ |
| D | Kconfig | 415 in a new file format that also logs the process IDs of each
|