From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 194607] New: Unable to change passwd upon a hard reboot
Date: Thu, 16 Feb 2017 15:00:32 +0000 [thread overview]
Message-ID: <bug-194607-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=194607
Bug ID: 194607
Summary: Unable to change passwd upon a hard reboot
Product: File System
Version: 2.5
Kernel Version: 3.18.29
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: ramanareddy1892@gmail.com
Regression: No
Hi,
I have an imx6dl based custom board. I compiled OpenWRT Chaos Calmer for this
and generated an image out of u-boot.img, zImage and dtb file in one partition
and rootfs in second partition. First partition is vfat and second(rootfs) is
ext4.
The board can boot from SD card and internal eMMC flash. I tried on both of
them.
Steps to reproduce:
1. Boot the image.
2. Change passwd to a non-empty string
3. Observe there is no passwd+ file in the /etc/ directory
4. Do a hard reboot (Soft reboot doesn't reproduce this)
5. Observe that passwd+ file exists in /etc/ directory. (Happens more than 80%
of the time)
6. Now unless we remove this file, passwd cannot be changed.
root@OpenWRT:~# passwd
Changing password for root
New password:
Bad password: too short
Retype password:
passwd: can't create '/etc/passwd+': File exists
passwd: can't update password file /etc/passwd
This cannot be a busybox issue. The problem comes because passwd+ file recovers
after it got deleted upon reboot!!
I will upload the required logs/docs/info if specified.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-02-16 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 15:00 bugzilla-daemon [this message]
2017-02-16 15:05 ` [Bug 194607] Unable to change passwd upon a hard reboot bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-194607-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox