Re: How to verify linux-next
On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: > On 10/01/17 09:44, Damian Tometzki wrote: > > > i resolved the issue with: > > sudo /etc/init.d/apparmor stop > > or boot with: apparmor=0 or systemctl mask apparmor ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to verify linux-next
On 10/01/17 09:44, Damian Tometzki wrote: > > Am Sonntag, den 01.10.2017, 21:58 +0530 schrieb Pintu Kumar: >> On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o >> wrote: >>> >>> On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: I need to submit a patch to mainline which should be verified against linux-next tree with latest API. >>> If you want to verify a patch that you intend to submit upstream, >>> my >>> suggestion is to *not* use linux-next, but rather use the latest >>> tagged -rc from Linus's tree. So for example, you might want to >>> use >>> v4.14-rc2 as your base, and then apply your patch on top of v4.14- >>> rc2. >>> And then test v4.14-rc2. That way you don't need to worry about >>> debugging problems that might be caused by code in other people's >>> development trees. >>> >>> If you know which subsystem tree your commit is going to be sent >>> to, >>> you might use as your base the current development branch of that >>> subsystem tree. But in general, it's fine to use something like >>> v4.14-rc2; if the subsystem maintainer you plan to be submitting >>> your >>> patch has other preference, he or she will let you know, or take >>> care >>> of rebasing your patch onto his subsystme tree. >>> My patch is related to some test utility based on client/server model. So, I need 2 terminal, one for server and one for client. >>> That implies you're running the commands to run the test by >>> hand. In >>> the ideal world, tests should be automated, even those that are >>> using >>> client/server so that tests can be run unattended, over and over >>> again. >>> >>> For example, here's an example of test involving a client and a >>> server >>> in xfstests: >>> >>> https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/g >>> eneric/131 >>> >>> See? No terminal required, and certainly not two terminals! >>> >>> Remember, it's important not just to run one test, because the risk >>> is >>> that fixing one bug might cause a test regression somewhere >>> else. So >>> when I "validate" a kernel, I'm running thousands of tests, just to >>> test the ext4 file system. For each bug that we fix, we try to add >>> a >>> new automated test, so we can be sure that some future change >>> doesn't >>> cause a bug to reappear. And if you're running hundreds or >>> thousands >>> of tests, you certainly aren't going to be wanting to manually set >>> up >>> each test by using putty to login to the VM using ssh! >>> 1) How to resolve linux-next build error with ubuntu virtual box 5.1.28 >>> Virtual box is not relevant. What is relevant is the kernel config >>> file you are using, and what compiler version / distro are you >>> using >>> to build the kernel. And as I said, you're better off using >>> something >>> like v4.14-rc2 instead of linux-next. >>> >> Ok thank you so much for your reply. >> Now I am able to boot with v4.14-rc2. But now I am facing another >> problem. >> Now, I am not able to connect to internet from virtual box. >> When I switch back to the default 4.10 the internet works normally. >> I think the dlclient stopped working. >> I am getting continuous logs related to apparmor like this: >> apparmor="DENIED" comm=dhclient >> apparmor="DENIED" comm=cups-browsed >> >> With 4.10, I tried installing apparmor-utils and then reboot with >> 4.14-rc2, but it did not help. >> Any suggestions on this? > > Hello, > > i resolved the issue with: > sudo /etc/init.d/apparmor stop or boot with: apparmor=0 -- ~Randy ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to verify linux-next
Hello, Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 Host: Windows 10 Guest: Ubuntu 16.04 Best regards Damian Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletni...@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I have a general question. > > How do we normally verify linux-next tree? > The same exact way you "verify" any other Linux kernel, for whatever > definition of "verify" you plan to use. > > > > > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next > > kernel is not booting. > Does an Ubuntu kernel boot correctly under VirtualBox? If not, fix > that issue first. Also, "is not booting" isn't detailed enough for > anybody > to make even a guess as to what's wrong. > > Also, note that 5.1.28 is out. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to handle Hotplug with UIO userspace driver
Hi Mandeep, Recently i encountered similar issue with UIO framework in hotplug scenario. I reviewed the earlier patch from 2010 and your 4 patch series. 4 patch series seems to work. I checked the latest kernel source and i dont think your patches have been merged. Hopefully i am not looking at the wrong place. If they are not merged is there a plan to merge them ? I do think these patches are required. I also found a bug in your patch set which is discussed here https://lkml.org/lkml/2017/6/14/30. I was able to workaround/fix it. I can upload a patch if needed. Please advice if you plan to get the patchset merged. Thanks Divakar ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to verify linux-next
Hello, i can tell you ubuntu 16.04 works under virtualbox 5.1.28 with the current linux-next kernel My maschine: Host: Windows 10 Guest: Ubuntu 16.04 Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletni...@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I have a general question. > > How do we normally verify linux-next tree? > The same exact way you "verify" any other Linux kernel, for whatever > definition of "verify" you plan to use. > > > > > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next > > kernel is not booting. > Does an Ubuntu kernel boot correctly under VirtualBox? If not, fix > that issue first. Also, "is not booting" isn't detailed enough for > anybody > to make even a guess as to what's wrong. > > Also, note that 5.1.28 is out. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to verify linux-next
** Re sending ** Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next kernel. So I am trying to find alternative ways, like using the virtual box or qemu-arm. 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next kernel is not booting. 2) For qemu-arm (versatilepb), I am able to build the kernel, but I could not figure out which rootfs to use with it. I tried creating minimal rootfs using busybox, but it does not contain enough interface. I am not able to open multiple terminal and also could not setup ssh to access it using PUTTY. So, if you know of any better rootfs to use with qemu-arm please let me know. Or, if you know of any better option to use linux-next please tell me. It will be really helpful. Thank You! Regards, Pintu On Fri, Sep 29, 2017 at 3:12 PM, Pintu Kumar wrote: > Hi, > > I have a general question. > How do we normally verify linux-next tree? > > I wanted to work on linux-next but I am facing some issues. > I could able to build linux-next for both x86 and arm, but I could not > verify it on any machine. > Currently I don't have a real Linux PC to boot with linux-next kernel. > So I am trying to find alternative ways, like using the virtual box or > qemu-arm. > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next > kernel is not booting. > 2) For qemu-arm (versatilepb), I am able to build the kernel, but I > could not figure out which rootfs to use with it. > I tried creating minimal rootfs using busybox, but it does not contain > enough interface. I am not able to open multiple terminal and also > could not setup ssh to access it using PUTTY. > > So, if you know of any better rootfs to use with qemu-arm please let me know. > Or, if you know of any better option to use linux-next please tell me. > It will be really helpful. > > > Thank You! > Regards, > Pintu ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to verify linux-next
On Mon, 02 Oct 2017 10:11:34 +0200, Kamil Konieczny said: > What about /usr/bin/ssh as init replacement ? Well, if you are OK with your system panicking right away. :) (Hint - the init process needs to be something that can run as a daemon). If you use /usr/sbin/sshd, that has a *slightly* better chance of working, except then you will need a *lot* of custom coding in your initramfs to do all the system setup usually done by init during boot - mounting file systems, configuring network interfaces, etc etc etc. Plus, sshd probably doesn't have some of the code needed for a true init process, such as reaping child processes it didn't spawn itself, cleanly shutting down/rebooting, and so on... pgpCGJyupwqr8.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to verify linux-next
On 29.09.2017 17:45, valdis.kletni...@vt.edu wrote: > On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said: > >> 1) If you have pointers on how to setup ssh/net connection on QEMU >> with busybox, do let me know. > > Busybox doesn't do that as far as I know, as it's intended as a single-user > /sbin/init replacement. You'll need a full-featured userspace with an actual > init daemon (sysvinit, systemd, etc) and an ssh daemon (openssh, or if you > want [...] What about /usr/bin/ssh as init replacement ? -- Best regards, Kamil Konieczny Samsung R&D Institute Poland ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
