Bug 1647159 - UDF does not respect console log level when DVD is mounted
Summary: UDF does not respect console log level when DVD is mounted
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-06 18:54 UTC by Steve
Modified: 2019-02-21 21:07 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:07:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steve 2018-11-06 18:54:39 UTC
Description of problem:
When the console log level is set to "crit" (for example), UDF logs an "INFO" message when a DVD is mounted:

Nov 06 10:16:39 xxxxxx kernel: UDF-fs: INFO Mounting volume 'Telescope', timestamp 2010/04/26 21:23 (1000)

That makes it impossible to disable logging of DVD titles, which can compromise user privacy.

Version-Release number of selected component (if applicable):
kernel-4.18.16-100.fc27.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Tile two terminal windows. In one window, run "journalctl -f".

2. In the other window, run the following commands (as root):

# cat /proc/sys/kernel/printk # verify current console log level
# dmesg -n crit # change log level
# cat /proc/sys/kernel/printk # verify new console log level ("3" in this example)

Insert a DVD and mount it:
# mount /dev/sr0 /mnt/dvd

Actual results:
An "INFO" message is logged:

Nov 06 10:16:39 xxxxxx kernel: UDF-fs: INFO Mounting volume 'Telescope', timestamp 2010/04/26 21:23 (1000)

Expected results:
No "INFO" message is logged.

Additional info:
The "INFO" message appears to be coming from fs/udf/super.c.

$ man 2 syslog

Comment 1 Steve 2018-11-06 20:59:22 UTC
NB: I have all automount functionality disabled. That includes the removal of the udisks2 and gvfs packages:

# dnf list --installed udisk\* gvfs\*
Error: No matching Packages to list

Comment 2 Steve 2018-11-13 15:05:59 UTC
Reproduced with F29.

Note that the "quiet" kernel command-line argument sets the console log level to "3":

$ cat /proc/sys/kernel/printk
3	4	1	7

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.18.17-300.fc29.x86_64 root=UUID=nnn ro resume=UUID=nnn rhgb quiet

That is inconsistent with "man 2 syslog", which says:

'console_loglevel ... is set to 4 if the kernel command line contains the word "quiet", ...'

Comment 3 Jeremy Cline 2018-12-03 17:31:41 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora 29 has now been rebased to 4.19.5-300.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 4 Steve 2018-12-04 08:59:46 UTC
UDF still logs an INFO message when the log level is set to "crit", and a DVD is mounted:

$ uname -r
4.19.5-300.fc29.x86_64

$ cat /proc/sys/kernel/printk
3	4	1	7

$ journalctl -k -g UDF -q --no-hostname
Dec 04 00:37:38 kernel: UDF-fs: INFO Mounting volume '[DVD title removed]', timestamp 2099/01/01 11:22 (1000)

Comment 5 Justin M. Forbes 2019-01-29 16:13:32 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 6 Justin M. Forbes 2019-02-21 21:07:02 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.